Migrate from ContactWise CRM to Microsoft Dynamics 365 Sales

ContactWise Contact records map directly to Dynamics 365 Contact. We preserve standard fields including name, email, phone, address, and any associated owner. Custom contact properties are identified during scoping, destination custom fields are pre-created in Dynamics 365 with matching data types before import, and value transformations are applied for data type differences (such as converting ContactWise multi-select picklists to Dynamics multi-select option sets). Owner assignment resolves by email match against the destination Dynamics User table.

ContactWise Lead records map to Dynamics 365 Lead. Lead status and source attribution migrate as custom or standard fields in Dynamics. The Dynamics Lead Status field uses the organization's configured status values, which we configure during schema setup. Lead score and qualification data from ContactWise custom fields migrate to corresponding custom fields on the Dynamics Lead object.

ContactWise Opportunity records map to Dynamics 365 Opportunity with deal name, amount, stage, expected close date, and owner preserved. The pipeline stage mapping is handled through a Dynamics Record Type and Sales Process configuration that we deploy before migration. Closed-Won and Closed-Lost reasons from ContactWise custom fields migrate to Opportunity custom fields in Dynamics.

ContactWise pipeline stage definitions are documented during discovery and mapped to Dynamics Sales Process stage values. Each Dynamics Sales Process is associated with an Opportunity Record Type, and the stage probability percentages migrate to Dynamics StageProbability fields. Stage names are mapped via a written mapping table created during scoping.

ContactWise Company records map to Dynamics 365 Account. Company name and address fields correspond directly. Account is created before Contact import so that the parent CustomerId or ParentAccountId lookup is satisfied at the moment of Contact insert. Owner assignment migrates by email resolution against the Dynamics User table.

ContactWise service desk tickets do not map directly to any standard Microsoft Dynamics 365 Sales object. Sales Cloud does not include a native ticket entity; Cases belong to Service Cloud. We create a custom Dynamics entity or extend the Account object with custom ticket fields to receive the ContactWise ticket schema. Every ticket attribute (subject, description, status, priority, created date, closed date, contact reference) is explicitly mapped. The original ContactWise ticket ID is preserved in a custom field for audit trail. Ticket-to-contact associations use the contact reference ID carried through the migration.

ContactWise Workflows store automation logic as platform configuration, not as data records. We cannot export and replay these rules. During discovery we document every active workflow (trigger type, conditions, actions, and associated objects), produce a written inventory with recommended Microsoft Dynamics 365 Sales Flow or Power Automate equivalents, and hand off the inventory to the customer's admin. Workflow rebuild is outside migration scope.

ContactWise documents and attachments associated with Contacts, Opportunities, or Tickets are exported to cloud storage (Azure Blob or customer-specified destination) and linked via SharePoint document locations in Dynamics 365 or as Note/Attachment records on the parent entity. The parent record must exist in Dynamics before attachment import, enforcing the dependency order. File metadata (filename, created date, author) is preserved in the SharePoint location or Dynamics Note.

ContactWise time entries linked to Contacts, Tickets, or Projects are exported with their association metadata. Because Microsoft Dynamics 365 Sales does not include a native time-tracking entity, we create a custom TimeEntry entity in Dataverse or attach time entries as Notes on the parent record with structured body content. The customer selects the preferred approach during scoping.