Migrate from Inmovilla to Microsoft Dynamics 365 Sales

Inmovilla prospects who have progressed to a deal or have an associated property interest map directly to Dynamics 365 Contact. The Contact gets linked to an Account via the primary owner agency. Email, phone, address, and name fields map field-for-field; the original prospect ID is stored as Original_Contact_Id__c on the record.

Inmovilla prospects who are early-stage (inquiry only, no property interest attached) route to Dynamics 365 Lead. FlitStack uses the presence of an associated property record as the split criteria: prospects with no linked property go to Lead; prospects with a linked property go to Contact and attach to the Opportunity.

Inmovilla's agency or broker company records map to Dynamics 365 Account. Account.Name, website, industry (mapped to Dynamics pick-list), and employee count map directly. Parent agency hierarchies (if Inmovilla stores agency networks) map to Account.ParentAccountId in Dynamics. The original Inmovilla company ID is preserved in a Source_System_ID__c custom field for audit traceability.

Inmovilla's Property entity has no direct equivalent in Dynamics 365 Sales — real estate listing data (property type, price, status, square meters, bedrooms, energy rating, zone) is migrated into a custom Dataverse table named RealEstateProperty. This table is linked to the Account or Contact that owns the listing via a lookup field.

Inmovilla owner and agent records map to Dynamics 365 SystemUser. FlitStack resolves each Inmovilla owner by email to an existing Dynamics 365 user; unmatched owners are flagged before migration. The original owner ID is preserved as a custom field (Original_Owner_Id__c) on all records that reference that owner, enabling audit traceability.

For Inmovilla owners who have no corresponding email in Dynamics 365, FlitStack creates a custom text field (Original_Owner_Id__c) on the Opportunity and Contact records to preserve ownership history. These records are assigned to a fallback user designated by the client before migration begins.

Inmovilla's prospect-to-property associations (which prospects are interested in which listings) are a junction relationship. FlitStack converts these into Dynamics 365 Opportunity records — one Opportunity per prospect–property pair — with the property linked via the custom RealEstateProperty lookup and the prospect linked as the Contact on the Opportunity.

Inmovilla activity history — calls, emails, meetings, and notes attached to prospects or properties — migrates to Dynamics 365 Activity records (Task for calls and generic activities, Email for email logs, Appointment for meetings). Original timestamps, owners, and parent record links (Contact or Opportunity) are preserved. Notes migrate to Dynamics 365 Notes (not legacy Note). Rich-text formatting in Inmovilla notes is downloaded and rehosted as file attachments in Dynamics.

Inmovilla attachments (images, PDFs, floor plans) are extracted and re-uploaded to the Dynamics 365 record's SharePoint document location. If the organization uses SharePoint integration, files land in the appropriate Account or Opportunity document library. File size limits from Dynamics apply; files exceeding 25 MB are flagged for manual handling.

Inmovilla tags applied to properties (e.g., 'reduced price', 'exclusive', 'investor-grade') have no native Dynamics 365 equivalent. FlitStack consolidates all tags into a multi-select text custom field (Property_Tags__c) on the RealEstateProperty table. Clients can optionally convert these to a custom pick-list in Dynamics after migration.