Migrate from Inmovilla to HighLevel

Direct 1:1 mapping. Inmovilla contacts migrate to HighLevel contacts with name, email, phone, address, and custom properties preserved. Owner resolved by email match to a HighLevel user — unmatched owners flagged before migration commits. During migration, duplicate detection runs on email addresses to prevent creating multiple records for the same contact.

Direct 1:1 mapping. Inmovilla company records (agency name, NIF/CIF, address, sector) map to HighLevel companies. Parent-child company relationships in Inmovilla translate to a parent company lookup in HighLevel's company record. The NIF/CIF identifier is stored as a custom field to maintain Spanish fiscal compliance and enable future integrations with Spanish business registries.

HighLevel has no native property object. FlitStack AI creates a Property__c custom object in HighLevel and maps every Inmovilla property field — price, type (venta/alquiler), surface area (m2), bedrooms, bathrooms, energy certificate, and listing status — as typed custom fields on the custom object.

Inmovilla's native portal-syndication links (Idealista, Fotocasa, etc.) have no HighLevel equivalent. We preserve the portal URLs and listing IDs as custom text fields on the Property__c record for reference — re-publishing to portals must be handled manually after migration. FlitStack AI provides an export file with all portal URLs formatted for re-upload into your syndication tool of choice.

Inmovilla's virtual tour and biometric signature fields store external URLs. These map as text fields on Property__c. Any embedded media links are preserved as strings; the actual media must remain hosted at the original URL or be re-uploaded to HighLevel's file storage.

Direct 1:1 mapping at the object level. Inmovilla deals (operaciones) become HighLevel opportunities. The deal name, associated contact, amount, and close date carry over directly. Pipeline and stage assignment requires a value-mapping step described in the field mapping section. The associated property reference links each opportunity to its corresponding Property__c record for complete deal context.

Each Inmovilla deal pipeline maps to a HighLevel pipeline. HighLevel allows multiple pipelines with custom stages, so the pipeline name and stage structure are preserved. If Inmovilla uses a single pipeline, it maps directly; multiple Inmovilla pipelines each get their own HighLevel pipeline.

Inmovilla tasks and follow-ups migrate as HighLevel tasks with original create date, due date, assigned user, and task body preserved. Status mapping: pendiente → not started, en curso → in progress, completada → completed. Tasks linked to specific contacts or properties carry those associations forward, enabling your team to trigger HighLevel workflows based on migrated task events.

Inmovilla notes migrate to HighLevel notes attached to the corresponding contact or company record. Rich-text formatting is preserved where Inmovilla's export supports it. Notes without a parent record are attached to the most recently associated contact. After migration, notes remain searchable in HighLevel's activity feed and can be referenced in workflow automations.

Inmovilla owner IDs do not map directly to HighLevel user IDs. Resolution uses email as the join key: each Inmovilla owner email is matched against HighLevel user email addresses. Unmatched owners are flagged with the owner name and email so your team can create or invite the user to HighLevel before migration.

Inmovilla supplier records map to HighLevel companies with a Supplier tag applied. This preserves the relationship without requiring a separate object — contacts linked to the supplier company are migrated normally and the tag is searchable in HighLevel. The Supplier tag enables filtering supplier companies in list views and can trigger workflow actions for procurement-related communications.

Inmovilla property owner records migrate as HighLevel contacts with a Property_Owner tag. The tag enables segmentation for owner communications and distinguishes these contacts from buyer/tenant contacts in HighLevel's contact list. Owner-tagged contacts can be included in property update broadcasts and maintenance notification workflows after migration.