Migrate from Cordis CRM to Microsoft Dynamics 365 Sales

Cordis CRM Contacts map directly to Microsoft Microsoft Dynamics 365 Sales Contact records. We resolve the Account relationship by matching the source Contact's associated Company or Profile name to a destination Account, creating the Account if it does not exist. External IDs from Cordis CRM export are preserved in a custom field for deduplication. Email, phone, address, and standard profile fields map to their typed Dynamics 365 equivalents.

Cordis CRM Company records and Profile entities map to Microsoft Microsoft Dynamics 365 Sales Account. We use the Company name or Profile name as the Account Name and domain or website as the Account Website field. Account is inserted before any Contact records to satisfy the required AccountId lookup on Contact. Any contact-company relationship graph from Cordis CRM is preserved through the Account-Contact linkage in Dynamics 365.

Cordis CRM Pipelines and associated Deals map to Microsoft Dynamics 365 Sales Opportunity records. We map the source pipeline name to a Microsoft Dynamics 365 Sales Process and Record Type, and the source stage names map to StageName values on the Opportunity. Probability percentages, close dates, and deal values migrate directly. Owner assignment resolves by email match against the destination Dynamics 365 User table.

Cordis CRM Campaigns map to Microsoft Dynamics 365 Sales Campaign records with campaign type, status, and dates preserved. Campaign Members from Cordis CRM migrate to Campaign Members in Dynamics 365, linked by email match to the corresponding Contact or Lead. We insert Campaigns before Campaign Members to satisfy the required CampaignId lookup during member import.

Cordis CRM Tasks (both automated and manual) map to Microsoft Dynamics 365 Sales Task records. Task Subject, Status, Priority, and ActivityDate migrate directly. Owner assignment resolves via email match to the destination User table. Recurrence rules from Cordis CRM are flagged as a gap because Microsoft Dynamics 365 Sales does not support recurring tasks natively; the customer's admin reconfigures recurring task patterns as needed.

Cordis CRM documents attached to records map to Microsoft Dynamics 365 Sales Notes (the older Note object) linked via ContentDocumentLink to the parent Contact, Account, or Opportunity. We extract the document content and filename, re-associate it using the record mapping table generated during the migration, and flag that only the latest version of each document migrates. Document version history beyond the current version is not available in the Cordis CSV export.

Cordis CRM custom fields on Contacts, Companies, Deals, and Campaigns migrate to custom fields in Microsoft Dynamics 365 Sales . Cordis CRM does not publicly document its custom field data types, so we survey the customer's instance during scoping to identify all active custom fields, infer their types from the exported data, and map them to the appropriate Dynamics 365 field type (text, number, date, picklist, or checkbox). Custom fields are pre-created in the destination org schema before data import begins.

File attachments linked to Cordis CRM records (Contacts, Companies, Deals) migrate as Salesforce Attachment equivalents in Dynamics 365, stored on the parent record with filename preservation. We extract each attachment, map it to the corresponding parent record using the record ID mapping table, and re-associate it post-import. Attachments that exceed Dynamics 365 file size limits are flagged for manual re-upload after migration.