Migrate from Inmovilla to HubSpot

Inmovilla contact records map directly to HubSpot contacts. Name, email, phone, job title, address, and create date are carried over. Owner resolution runs by email match against HubSpot users before insertion. All contact IDs are stored in a custom Source_System_ID__c field for duplicate detection and future delta runs. Any missing required HubSpot fields are flagged for pre‑migration cleanup.

Inmovilla does not split leads and contacts into separate objects. All records land as HubSpot contacts with a custom lifecycle_stage property (Inmovilla_Client_Type__c) set to 'Cliente' or 'Lead' so segmentation by client type is preserved in HubSpot's contact list views. The custom property is created during the pre‑migration schema setup and populated from Inmovilla's tipo_cliente field. Any missing values are logged for review.

Inmovilla company records (agencies, property management firms, landlord companies) map to HubSpot companies. Company name, domain, industry, employee count, and annual revenue transfer directly. HubSpot's Parent Company field maps from Inmovilla's hierarchy if parent‑child relationships exist. Any missing required fields such as industry are flagged for pre‑migration enrichment. The mapping preserves the original Inmovilla company ID in a custom Source_System_ID__c field.

Inmovilla's primary real estate record has no direct HubSpot equivalent. We create a Property custom object on HubSpot (Professional+) and map all property-specific fields — type, meters, bedrooms, bathrooms, price, energy rating, listing reference — as custom properties. The custom object must be created before migration begins.

Inmovilla stores N:N links between contacts and the properties they own, are interested in, or have visited. HubSpot has no native many-to-many contact-property association. We create a junction custom object with Contact lookup and Property lookup fields to preserve every association.

Inmovilla reservation deals (reserva) migrate as HubSpot deals. Deal name, amount, and close date map directly. The dealstage value (Reservation, Option, Contract, Sale Closed) maps via value mapping to the corresponding HubSpot pipeline stage name. Each stage's probability is configured in HubSpot's pipeline settings before migration. Any unmatched stage values are flagged for manual assignment. The original Inmovilla deal ID is stored in Source_System_ID__c for reconciliation.

Inmovilla's reservation stages map one-to-one to a HubSpot deal pipeline named 'Real Estate Sales'. Each stage gets its own stage probability value configured in HubSpot's pipeline settings. We apply the mapping before the migration run so deal records land with the correct stage immediately.

Inmovilla deals reference a property record directly. Since the property is a custom object in HubSpot, we add a Property_v2__c lookup field on the Deal object (requires a custom deal-property association schema). This field is empty at migration time and populated after both objects exist in HubSpot.

Inmovilla agent IDs are resolved by email address against HubSpot user accounts. Agents without a HubSpot account are flagged before migration; their records can be assigned to a fallback HubSpot user or their accounts created before the final run. The resolution uses a lookup table built from Inmovilla's user export, ensuring that each deal and contact owner is matched accurately. Unresolved owners are logged with record counts for follow‑up.

Inmovilla call logs, emails, and meeting records attached to contacts and properties migrate as HubSpot engagements. Call logs become Tasks with type 'Call', emails as Emails, and meetings as Meetings. Original timestamps and agent owners are preserved. Each engagement stores the Inmovilla record ID in a custom Source_System_ID__c field for audit trails and duplicate detection.

Inmovilla notes on contacts, properties, and deals become HubSpot engagement notes. The note body and create timestamp transfer directly. Notes attached to property records reference the Property custom object after the junction schema is live. The original Inmovilla note ID is stored in a custom Source_System_ID__c field for traceability.

Inmovilla properties carry links to external listing portals (idealista, fotocasa, etc.) stored as URL fields. These portal links have no HubSpot equivalent and are stored as a custom text property (Portal_Links__c) for reference — they are not functional after migration.