Migrate from Acquaint CRM to Microsoft Dynamics 365 Sales

Acquaint contacts map directly to Dynamics 365 Contacts. Dynamics 365 requires an AccountId (lookup to Account) for most contact records — contacts without a primary company in Acquaint are attached to a default 'Unassigned Account' record or held as Leads based on lifecycle status. Email addresses are used for owner resolution and duplicate detection.

Acquaint company records map to Dynamics 365 Accounts 1:1. The company name becomes Account.Name, domain/website maps to Website, and address fields map to the composite address fields (Address1_Line1, City, StateOrProvince, PostalCode, Country). Acquaint's parent/child company hierarchy maps to Account.ParentAccountId where present.

Acquaint deal records map to Dynamics 365 Opportunities. Each Acquaint deal pipeline maps to a Dynamics 365 Sales Process (processid on the Opportunity). Pipeline stage names map to Opportunity StageName pick-list values per Sales Process. Deal amount maps to Opportunity Amount; close date maps to CloseDate.

Acquaint property listings have no native Dynamics 365 equivalent. FlitStack AI creates a new_Property custom table in the target Dataverse environment with columns for address, property type, listing status, price, and reference to the owning Account. Floor plans, virtual tours, and photographs are downloaded from Acquaint and rehosted in SharePoint or Dataverse file storage with URL references stored on the new_Property record.

Acquaint tasks and reminders map to Dynamics 365 Tasks as a direct 1:1 translation. All core metadata is preserved — original created dates, due dates, assigned owners, and subject lines transfer unchanged. Tasks linked to a specific contact or deal carry the regarding_objectid lookup to maintain the parent relationship in Dynamics 365. Recurring task patterns in Acquaint are flagged for Power Automate rebuild since recurring calendars do not export in a portable format.

Acquaint notes map to Dynamics 365 Notes using the notedata body field for content storage. Rich-text formatting is preserved where the API returns HTML-formatted note bodies. Notes attached to specific records carry the objectid lookup to restore parent context in Dynamics 365. Large note volumes — common in property CRM setups with long transaction histories — require batched API reads with pagination offsets from Acquaint to avoid request timeouts during export.

Acquaint's multi-branch and franchise model uses in-app staff permissions scoped per branch. Dynamics 365 uses Business Units for data partitioning and Security Roles for access control. FlitStack AI maps each Acquaint branch to a corresponding Business Unit in Dynamics 365, then assigns the Security Role to users during the owner-resolution step. Business Units must be pre-created in Dynamics 365 before migration.

Acquaint's client accounting, bank imports/exports, and branded document/e-signing features have no equivalent in Dynamics 365 Sales. These must be either (a) archived as CSV exports before migration, or (b) migrated to Dynamics 365 Business Central separately. FlitStack AI flags these as archival candidates and provides an export-for-handoff package rather than loading them into Dynamics 365 Sales.

Acquaint custom fields on any entity map to custom columns on the corresponding Dynamics 365 entity or to custom table rows for property-specific fields. Custom column names in Dataverse follow the new_customfield naming convention. Data types are mapped: text to nvarchar, number to integer or decimal, date to datetime, pick-list to choice. Custom fields must be pre-created in Dynamics 365 before the migration validation run.

Acquaint staff records (owner assignment on deals, contacts, properties) are resolved by email match against Dynamics 365 SystemUser records. Unmatched owners are flagged before migration and assigned to a fallback owner or held for manual assignment. This step is critical for multi-branch setups where staff permissions differ by branch.

Acquaint file attachments (floor plans, EPCs, virtual tour links, property photographs) are downloaded via the Acquaint API and rehosted in SharePoint document libraries linked to the target Account or new_Property record. The SharePoint URL is stored in a custom column on the Dynamics 365 record. File size limits from Dynamics 365 Dataverse apply.

Acquaint SMS text records have no native Dynamics 365 equivalent. FlitStack AI migrates SMS content as a custom text column (new_SMSText) on the Contact record or as a Note with the SMS label in the subject, preserving the original send date, recipient, and message body for audit purposes.