Migrate from Sage CRM to Microsoft Dynamics 365 Sales

Sage CRM Companies map to Microsoft Microsoft Dynamics 365 Sales Account records. The Company name becomes Account Name, the primary address maps to the Account's primary postal address fields, and any secondary addresses (billing, shipping, branch offices) must be consolidated into a single primary address or stored as related Address records. Industry, classification, and custom Company fields map to corresponding Account fields or custom fields on Account. We create Account records first during migration so that the parent-record lookup is satisfied for all dependent Contact imports.

Sage CRM Contacts link to Companies via the PrimaryCompanyLink foreign key. We resolve this relationship at migration time by first loading Companies into Dynamics 365 as Accounts, then mapping PrimaryCompanyLink to the AccountID on each Contact. Custom Contact fields and Sage CRM's person-type fields map to custom Contact fields in Dynamics 365. Duplicate detection uses email address as the primary dedupe key with phone number as a secondary match.

Sage CRM Leads map to Microsoft Microsoft Dynamics 365 Sales Lead records. Lead qualification status, source tracking, and custom lead fields migrate directly. The Dynamics 365 Lead includes a leadqualitycode and leadsourcecode field that we populate from Sage CRM's lead status and source fields. Dynamics 365's Lead does not require an immediate Convert action, but the customer decides during scoping whether existing Sage CRM Leads that represent qualified buyers should be pre-converted to Contact-Account pairs rather than loaded as Leads.

Sage CRM Opportunities map to Microsoft Dynamics 365 Sales Opportunity records. Pipeline stages, revenue amounts, expected close dates, and owner assignments migrate with stage probabilities recalculated to match the customer's Microsoft Dynamics 365 Sales Process stage weights. Multi-currency amounts in Sage CRM (if the customer's deployment supports multiple currencies) are stored in the currency fields and map to the Dynamics 365 closeprobability and estimatedvalue fields. Custom opportunity fields migrate as custom fields on Opportunity.

Sage CRM pipeline configuration (named pipelines and their stage sequences) maps to Dynamics 365 Record Types and Sales Processes. Each Sage CRM pipeline becomes a Dynamics 365 Record Type on Opportunity, with a corresponding Sales Process that whitelists the stage values. Stage probability percentages migrate from Sage CRM to Dynamics 365 StageProbability with rounding to the nearest integer allowed by the platform.

Sage CRM Cases map to Microsoft Dynamics 365 Sales Case records. Case severity, status, and owner assignment migrate. Threaded Communications attached to a Case are stored in the Sage CRM Communication table linked by CaseID; we export these Communication records and attach them to the corresponding Dynamics 365 Case as EmailMessage records or as Notes linked to the Case, preserving the chronological sequence of case interactions.

Sage CRM Communication records are entity-type agnostic, linked to Company, Contact, Lead, Opportunity, or Case. We export Communications, determine the target entity type, resolve the Dynamics 365 record ID for the parent reference, and load into the corresponding Dynamics 365 object: emails as EmailMessage linked to Tasks, call records as Task with TaskSubtype=Call, meetings as Event records, and general notes as Note records. The migration target for Communications is Microsoft Dynamics 365 Sales or Service Cloud depending on the customer's destination license.

Sage CRM Custom Entities have display names and internal table names (e.g., CustomEntityname) that we discover via the API model service. Each Custom Entity maps to a Dataverse custom table with a corresponding logical and physical name. All custom fields on the entity map to typed Dataverse columns. If the custom entity has lookup relationships to standard entities (Company, Contact, Opportunity), we pre-create those relationship columns in Dataverse and resolve the parent record ID during the migration transform step. Custom Entity data migrates after all standard entities to ensure parent-record lookup resolution.

Sage CRM Users with role-based security profiles map to Dynamics 365 User records by email address. Role assignments in Sage CRM (security profiles controlling object and field access) do not migrate directly because Dynamics 365 Security Roles are structured differently. We extract the user's role assignments as a written inventory and map them to the nearest equivalent Dynamics 365 Security Role during the security design phase. The customer's Dynamics 365 admin assigns Security Roles post-migration.

Sage CRM Reports stored in the report schema with internal entity field references are documented and exported during discovery. Report formatting, formulas, and scheduling do not migrate and must be recreated in Dynamics 365 using the report designer or Power BI. We deliver a report inventory documenting every Sage CRM report, its data source entities, filters, and output format so that the customer's admin or a Dynamics 365 partner can rebuild them in the new platform.