Migrate from Interactive to Microsoft Dynamics 365 Sales

Interactive contact records map directly to Dynamics 365 Contact. The primary company association in Interactive becomes the AccountId lookup in Dynamics. Contacts without a company link receive a placeholder AccountId or land under a designated fallback Account record. During migration, a placeholder AccountId ensures referential integrity and prevents orphan contact records.

Interactive contacts with a lifecycle stage indicating a non-customer prospect (e.g., 'lead', 'prospect', 'marketing qualified') route to the Dynamics 365 Lead entity. The original lifecycle value migrates as a custom field so no data is lost during routing. This preserves historical lead status for reporting and ensures that downstream Power Automate triggers that depend on the lead stage fire correctly in the new environment.

Interactive contacts that have reached a customer or active lifecycle stage map directly to Dynamics 365 Contact. Their final lifecycle status is preserved in a custom field, and their company association links via AccountId. This mapping ensures that existing customer relationships are fully represented in Dynamics 365, retaining all relevant contact details, activity history, and ownership assignments for ongoing service and upsell workflows.

Interactive companies map to Dynamics 365 Accounts. The parent-company hierarchy in Interactive (if used) maps to the ParentAccountId field in Dynamics. Multi-company contact associations in Interactive collapse to the primary Account lookup plus Account Contact Relationships in Dynamics. If a parent company does not yet exist in Dynamics, FlitStack creates a placeholder Account to satisfy the lookup before inserting child records, preventing referential errors during bulk ingestion.

Interactive deals map to Dynamics 365 Opportunities. Deal name becomes Opportunity Name, deal amount maps to Amount, close date maps to CloseDate, and owner resolves by email match to a Dynamics 365 user. Pipeline stage maps via a value-mapping table to StageName.

Each Interactive pipeline becomes a Dynamics 365 Sales Process. Stage names and probabilities map to StageName pick-list values and forecast category within that process. If multiple pipelines exist, we create corresponding Sales Processes in Dynamics before mapping data. This approach ensures that each deal’s progression through a pipeline is represented by the correct Sales Process in Dynamics, enabling accurate reporting, stage‑specific automation, and role‑based visibility.

Interactive stores lead lifecycle status as a contact property. In Dynamics 365, this becomes a custom pick-list field (Lifecycle_Stage__c) on both Contact and Lead, preserving all source values. For leads, the standard Status field is also populated with the closest equivalent value.

Interactive activity records (calls, emails, meetings) map to Dynamics 365 Task and ActivityPointer entities. Activity type is encoded in the ActivityTypeCode field. Original timestamps, owners, and parent-record lookups are preserved during migration. The migration also maintains the original subject, description, and any custom activity attributes, ensuring that historical interaction data is fully available for reporting and future automation triggers in Dynamics 365.

Interactive notes migrate to Dynamics 365 enhanced Notes (not the legacy Note object). Rich-text formatting is preserved where supported. Notes are linked to the parent record (Contact, Account, or Opportunity) using the RegardingObjectId lookup. During migration, FlitStack converts any unsupported HTML markup to plain text or preserves safe HTML tags, and it logs the original creation timestamp for audit purposes, ensuring compliance and traceability.

Interactive file attachments on records are downloaded and re-uploaded to Dynamics 365 Dataverse file storage (or SharePoint if the environment is SharePoint-connected). File size limits and inline image handling are applied per Dynamics storage policies. FlitStack also records the original upload date, file name, and MIME type as metadata in Dataverse, allowing users to search and filter attachments without relying on external storage locations.

Interactive custom objects map 1:1 to Dataverse custom tables in Dynamics 365 Sales. Custom object relationships that use Interactive's N:N association model need Dataverse many-to-many relationships or junction tables — we document this in the pre-migration schema plan. If a custom object references a parent Contact or Account, FlitStack creates the appropriate lookup field and validates foreign-key constraints before loading data, avoiding orphaned records and maintaining referential integrity.

Interactive owner records are resolved against Dynamics 365 SystemUser by email address. Unmatched owners are flagged before migration; your team either provisions the user in Dynamics first or assigns those records to a designated fallback owner during migration. This pre‑migration check prevents records from landing in an unmapped state and ensures that ownership assignments align with your current Dynamics user roster, supporting accurate reporting and task routing after cutover.

Interactive workflow rules and automation logic do not have a direct equivalent in Dynamics 365 Sales and cannot be auto-migrated. We export your Interactive workflow definitions as a structured JSON document that your Dynamics admin can use as a reference when rebuilding flows in Power Automate.