Migration to Tesoro: Your Data, Safely Transferred
Switching to Tesoro? The Tesoro team handles the migration, you don’t have to do it yourself. Sooprema and Inmoweb have ready-made connectors. Other CRMs? The Migration Toolkit is extensible.
When is this relevant?
Section titled “When is this relevant?”- You are considering switching from your current CRM to Tesoro
- You are preparing a migration conversation with the Tesoro team
- You are wondering if your old data will be 100% transferred
Supported CRMs
Section titled “Supported CRMs”JSON exports. Toolkit processes:
| Entity | Source file |
|---|---|
| Contacts | contacts-*.json |
| Owners | owners-*.json |
| Agents | agents-*.json |
| Notes | entries-*.json |
| Activities | activities-*.json |
| Scheduled activities | activities_scheduled-*.json |
| Properties | properties-*.json |
Automatic conversions:
- Phone numbers → international format (BE/NL/ES/DE/FR/UK)
- Language detection based on contact data
- Salutation (Mr/Mrs) auto-determined based on first name
- All fields to Tesoro format
Spanish CRM with XML exports.
| Entity | Source file |
|---|---|
| Contacts | contactos.xml (Cliente, Demandante, Propietario) |
| Properties | propiedades.xml |
| Search requests | demandas.xml |
| Portal inquiries | peticiones de informacion.xml (Idealista, Fotocasa, …) |
| Viewings | visitas.xml |
| Calendar | calendario.xml |
Automatic mapping:
- Contact types → Tesoro roles (Cliente/Demandante → Buyer; Propietario → Seller; Agente → Real Estate Agent)
- Spanish property types → Tesoro types (Piso → Apartment, Chalet → Villa, …)
- Portal source recognition (Idealista, Fotocasa, Habitaclia, Pisos.com)
- Client story reconstruction from viewings + search requests + inquiries
The migration process: five phases
Section titled “The migration process: five phases”-
Inventory: All files detected and counted. Baseline established per entity + status (active, hidden, deleted). Serves as a contract: after migration, counts must exactly match.
-
Analysis: Notes + activities per contact AI-analyzed. Reconstruction: cold lead? Previous contact? Viewing taken place? Offer made? Determines which Tesoro entities are needed.
-
Building profiles: Per contact a complete profile: personal data + analysis results + status + mapping to Tesoro entities.
-
Executing the migration: Profiles → Tesoro entities. Order is important:
- Properties (usually already via XML feed)
- Contacts (owners as sellers, contacts as buyers)
- Deals (with links)
- Notes (with source attribution)
- Activities
-
Verification: Counts vs baseline. ID-level: missing/duplicate? Sample of 10, 20 contacts manually.
2-step import strategy
Section titled “2-step import strategy”Prevents your pipeline from being polluted with thousands of old inactive leads.
Step 1: Leads import
Section titled “Step 1: Leads import”All contacts first imported as leads. AI classification:
| Classification | Criterion |
|---|---|
| Active | < 2 months old |
| To Deal | > 2 months + evidence of activity |
| Unqualified | > 2 months, lead without potential |
| Lost | > 2 months, no follow-up or potential |
Filterable in Tesoro by this classification.
Step 2: Deals conversion
Section titled “Step 2: Deals conversion”Filter on “To Deal” → team reviews → only approved leads are converted (with correct pipeline stage + property link).
What gets migrated
Section titled “What gets migrated”Layer A: Core (always)
Section titled “Layer A: Core (always)”- Contacts: with correct role (buyer, seller, real estate agent)
- Deals: only with evidence of activity
- Notes: with source attribution (source stamp)
- Links: contact-deal, deal-property
Layer B: Smart enrichment (optional)
Section titled “Layer B: Smart enrichment (optional)”- Viewings: reconstructed from notes + activities
- Tasks: follow-up for recent viewings (last 30 days)
- Reminders: follow-up actions for warm leads
Migration rules
Section titled “Migration rules”- Deleted records included, not visible, but counted for verification
- No auto-merge, duplicates reported, not automatically merged. You decide.
- Dates remain correct
- Source attribution on notes, reference to original CRM at the bottom
- Full traceability, original IDs preserved
Migration Pack: what you receive after completion
Section titled “Migration Pack: what you receive after completion”- Export analysis: baseline counts per entity + status
- ID Reconciliation Report: missing/extra/duplicate records per ID
- AI Analysis Log: model used, version, number of processed contacts
- Migration Verification Report: counts, ID verification, sample
- Sample files: 10 profiles for illustration
What you need to prepare
Section titled “What you need to prepare”-
Export your current CRM: full export of contacts, notes, activities. Tesoro team helps with export settings.
-
List of employees: names + email addresses for account creation and correct agent linking.
-
Reserve time for review: after migration you receive a report + sample check. ~1 hour.