Migrate from Inmovilla to Salesforce Sales Cloud

Inmovilla's primary listing record becomes a Salesforce Account of type 'Property' or 'Real Estate' depending on the agency's usage pattern. The property address maps to Account.BillingAddress. The listing status value maps to a custom pick-list field Listing_Status__c on the Account.

When the agency uses Inmovilla to track a listing as a revenue-generating deal (sale commission or rental management fee), the property merges into a Salesforce Opportunity representing the transaction. The property ID is preserved as Source_Property_ID__c for traceability back to Inmovilla.

Inmovilla client contacts map 1:1 to Salesforce Contacts. The Contact's AccountId lookup points to the primary property Account the client is associated with in Inmovilla. Multi-property clients require AccountContactRelation records for every additional property association. The primary property is the most recently modified listing in Inmovilla, ensuring the contact’s current focus is the primary Account. Additional property associations are stored as AccountContactRelation records, preserving the relationship type for each link.

Inmovilla contacts with no closed transaction or active listing association route to Salesforce Lead. Agents who are still prospect-facing with no confirmed engagement become Leads; confirmed clients with active or historical transactions become Contacts under an Account. This routing relies on Inmovilla's transaction status: contacts with a 'vendido' or 'alquilado' flag or an active listing become Contacts; all others become Leads, preserving the prospect pipeline.

Inmovilla agent records map to Salesforce Users via email-match lookup. We flag any Inmovilla owner without a matching Salesforce user email before migration and surface them in the pre-flight report so your admin can create the User or assign a fallback owner before data lands.

Inmovilla property owners — distinct from agent owners — map to Salesforce Contacts attached to the property Account, or to a separate Account if the owner is a company. Owner type (individual vs. company) determines whether Contact or Account is the target.

Inmovilla call logs (recorded interactions with clients or owners) migrate as Salesforce Tasks with Type='Call'. The original call timestamp, duration, and agent owner map to Task fields. ParentId links the Task to the corresponding Contact or Account. Call notes are stored in the Task Description field, and the OwnerId is resolved via email match to the corresponding Salesforce User. Each call maintains its original timestamp for activity reporting.

Inmovilla email activity records become Salesforce Tasks with Type='Email'. Subject line and body text migrate. Attachments are downloaded and re-uploaded to Salesforce Files linked to the parent Contact or Account record. The email’s send date maps to ActivityDate, and the body text is stored in the Description field. Attachments are linked via ContentDocumentLink to the parent Contact or Account, respecting Salesforce's file size limits of 25 MB per file.

Inmovilla property visit records and scheduled meetings migrate as Salesforce Events with original start/end times preserved. The event is linked to the Contact or Account and optionally to the Opportunity representing the transaction. Visit type values map to Event Type pick‑list, and the property address is stored in the Location field. OwnerId is resolved via email match, and visit notes are saved in Description.

Inmovilla notes on properties or clients become Salesforce Notes (the enhanced Notes object, not legacy Note). Rich-text formatting is preserved where possible. Notes are linked to the parent object — typically the property Account or the client Contact. The original creation timestamp is stored in CreatedDate, and any attachments are migrated as Salesforce Files linked to the same parent record, maintaining the complete note context.

Inmovilla custom listing fields (m², rooms, floor number, energy certificate rating, orientation, parking, storage) have no Salesforce standard equivalent. Each attribute becomes a custom field on the Account object, with the __c suffix naming convention applied. Pick-list attributes like energy certificate rating use Salesforce pick-list fields with value-by-value mapping to Inmovilla's allowed values.

Inmovilla stores URLs to Idealista, Fotocasa, and other Spanish real estate portals against each listing. These are non-clickable reference URLs in Salesforce. We store them in a multi-line custom text field (Source_Portal_URLs__c) on the Account so agents have visibility into where the listing was syndicated.

Inmovilla property documents (floor plans, title deeds, energy certificates) and client ID scans attached to contacts migrate as Salesforce Files. Files are linked to the parent Account or Contact record. File size limits (Salesforce default 25MB per file) apply; oversized files are flagged for manual handling.

Inmovilla portal-syndication rules, status-change auto-email triggers, and lead-distribution automations have no Salesforce equivalent that can be imported. We export the configuration definitions from Inmovilla as a structured reference document so your Salesforce admin can rebuild equivalent Flows in Salesforce. The export includes JSON schemas, screen captures, and trigger‑logic flowcharts to guide the admin in recreating the automation logic using Salesforce Flow, Process Builder, or Apex as appropriate.