Migrate from Acumen to Microsoft Dynamics 365 Sales

Acumen contacts with lifecycle stage equal to 'customer' or 'evangelist' map to Dynamics 365 Contact. All other lifecycle values (lead, prospect, subscriber) route to Dynamics 365 Lead. The split decision is made at migration time based on the Acumen lifecycle stage property value. Original stage history is preserved in Lifecycle_Stage_History__c as a text audit trail.

Acumen companies map directly to Dynamics 365 Accounts. Parent-company hierarchies in Acumen use the ParentId field in Dynamics to preserve the same relationship structure. Multi-company contacts that exist in Acumen as N:N associations are resolved to a primary AccountId plus Account Contact Relationships in Dynamics.

Acumen deals migrate as Dynamics 365 Opportunities with deal name becoming Opportunity Name, amount carrying over as Amount, and close date mapped to CloseDate. Pipeline assignment determines which Business Process Flow (Dynamics Sales Process) the opportunity is scoped under — this is set via the opportunity's ProcessId field.

Each Acumen pipeline becomes a Dynamics 365 Sales Process. In Dynamics, Sales Processes are tied to Business Process Flows that drive stage-by-stage progression through the UI. The Acumen pipeline's stage values map to Opportunity StageName pick-list values scoped within each Sales Process. This transformation requires your Dynamics admin to create the Business Process Flows before data loads.

Acumen stage names are mapped value-by-value to Dynamics 365 Opportunity StageName values within each corresponding Sales Process. Stage probability percentages, forecast categories, and stage-entered timestamps are stored as custom fields (Stage_Probability__c, Forecast_Category__c, Stage_Entered_Date__c) because Dynamics calculates probability automatically from Business Process Flow stage.

Acumen custom objects map 1:1 to Dataverse custom tables in Dynamics 365 Sales. Custom object schema names follow the new_ prefix convention (e.g., new_CustomObjectName). Custom-object-to-contact or custom-object-to-company associations that use Acumen's N:N model require Dataverse many-to-many relationship entities (many-to-many intersect tables) which FlitStack creates as part of the migration plan.

Acumen activity records are split into their Dynamics equivalents: calls and generic activities map to Task with Type='Phone Call', emails map to Email (or Task with 'Email' in Subject), meetings map to Appointment with original start and end times, and notes map to Annotation (Note). All parent-record links (regardingobjectid) are resolved to the migrated Dynamics record ID.

Acumen file attachments are downloaded and re-uploaded to a SharePoint document library linked to the target Dynamics 365 entity via SharePointDocumentLocation records. Inline images embedded in Acumen notes are extracted and hosted as SharePoint files with the note body updated to reference the new URL. Dynamics file size limits (25 MB default per file) are enforced during the upload.

Acumen owner IDs are resolved to Dynamics 365 users by email address match against the SystemUser table. Unmatched owners are flagged before migration with a fallback owner assignment option. Records without a resolved owner receive the designated migration placeholder owner so no record lands without an ownerid — Dynamics requires all owned records to have an owner set.

Acumen automation rules, sequences, and workflow logic do not have a structural equivalent in Dynamics 365 Sales and cannot be migrated. FlitStack exports the Acumen automation definitions as JSON configuration files that document trigger conditions, action steps, and filter logic. These exports serve as a functional specification for your Dynamics admin or consultant to rebuild the automation using Sales Processes, Power Automate flows, or Dataverse Business Rules.