Migrate from Inmovilla to Freshsales

Inmovilla client records map directly to Freshsales Contacts. Email, phone, and address fields map to Freshsales' standard Contact fields. Clients with no email address are flagged for manual review before migration — Freshsales requires an email for Contact creation via API.

Inmovilla clients who have not initiated a property transaction route to Freshsales Lead. The split is determined by whether the client has an associated property record with a transaction status — active transaction records land as Contacts, prospect-only records land as Leads.

Inmovilla's property entity has no direct Freshsales equivalent. We migrate property data as custom fields on the Contact record (Property_Type__c, Square_Meters__c, Energy_Certificate__c, Property_Reference__c) so each client contact carries their associated property details. Additional custom fields such as Parking_Space__c, Community_Fees__c, or Urbanization__c can be added similarly, preserving data type fidelity for reporting and segmentation.

Inmovilla transaction records map to Freshsales Deals. The transaction type (sale, rental, rental-with-option) maps to a Deal custom field (Transaction_Type__c). Freshsales' Kanban pipeline stages are created to reflect the transaction lifecycle stages in use at the time of migration. Each stage includes probability weights for accurate forecasting in Freshsales' deal analytics.

Inmovilla's property status values (disponible, reservado, vendido, alquilado) map to Freshsales Deal Stage pick-list values. Each status requires a value-by-value mapping entry — unrecognised status values default to a configurable fallback stage. The mapping table also records the Spanish labels, the corresponding English Freshsales stage names, and any probability adjustments required for pipeline forecasting.

Inmovilla agent assignments are resolved by email match against Freshsales users. If an Inmovilla agent has no corresponding Freshsales user account, their records are assigned to a fallback owner and flagged for your admin to create the user before go-live.

Property notes in Inmovilla migrate as Freshsales Notes attached to the associated Contact record. Original timestamps and creating agent are preserved as metadata on the Note. The note body retains full text, including any HTML formatting, and any linked attachments are logged with file size and mime type for downstream verification.

Inmovilla document attachments (property photos, floor plans, energy certificates) are downloaded and re-uploaded to Freshsales Files, linked to the corresponding Contact record. File size limits are enforced per Freshsales storage quota. Each file retains its original filename, creation date, and SHA‑256 hash for integrity checking, and is associated with the contact via Freshsales' file attachment API.

Inmovilla portal-synchronisation links to Spanish property portals (Idealista, Fotocasa, etc.) have no Freshsales equivalent. We preserve the last-known portal URL as a custom field (Last_Portal_URL__c) for reference, but the sync integration must be rebuilt using Freshsales' outbound webhook or a third-party integration.

Inmovilla's biometric signature capture for contract signing is a platform-specific feature with no Freshsales counterpart. We preserve the signature event metadata (date, contract reference) as a custom field on the Deal; the signature itself is not migratable and can be referenced in reports by linking to the contract document record.

Inmovilla custom property fields (e.g., urbanization name, floor number, parking space) are enumerated before migration. Each is created as a Freshsales custom field on Contact (client-specific) or Deal (transaction-specific), with data type preserved — text fields stay text, numeric fields stay numeric.