Migrate from NextCRM to Microsoft Dynamics 365 Sales

NextCRM Contact records map directly to Microsoft Dynamics 365 Sales Contact. We extract every standard field (firstname, lastname, email, phone, address) and custom field values from NextCRM's custom field system. Before Contact import, we provision the parent Account record so that the AccountId lookup is satisfied at insert time. If the NextCRM contact lacks a company association, we create a single Account using the contact's domain or a placeholder name and link it. The original NextCRM contact ID is preserved in a custom field nxcrm_original_id__c for audit and reconciliation.

NextCRM's Company data (plugin edition stores company name and domain on the Contact record) is extracted as a distinct set and mapped to Microsoft Dynamics 365 Sales Account. The Company name maps to Account Name, the domain maps to Website, and any billing or shipping address fields on the NextCRM contact map to the Account Address composite. We create Account records first in the migration sequence so that subsequent Contact imports have a valid parent lookup. Deduplication uses domain as the key for companies with multiple associated contacts.

NextCRM Tags migrate as either Microsoft Dynamics 365 Sales multi-select picklist fields on Contact (if fewer than 15 tags and all are CRM-relevant) or as text custom fields with tag names stored as comma-separated values. Tags used for marketing segmentation are preserved as a custom field and documented for the customer's admin to map to Microsoft Dynamics 365 Sales marketing lists or Power Automate flows if needed. We flag any tag that contains more than 100 unique values as a candidate for a separate related entity rather than a picklist.

NextCRM Lists and Advanced Segmentation rules transfer as Microsoft Dynamics 365 Sales Marketing Lists (static) or as saved Contact views with filter criteria documented for manual recreation as Microsoft Dynamics 365 Sales Advanced Find queries. Segment logic that relies on behavior triggers or revenue attribution cannot map directly because these features are NextCRM-specific; we document the original segmentation rule so the admin can rebuild it using Microsoft Dynamics 365 Sales filters and Power Automate conditions.

NextCRM Deals map to Microsoft Dynamics 365 Sales Opportunity. We map dealstage to StageName and any pipeline assignment to a Microsoft Dynamics 365 Sales Record Type or Sales Process that we configure before migration. Closed-Lost reason and Closed-Won reason from NextCRM custom fields become custom Loss Reason and Win Reason fields on Opportunity. The Deal amount maps to Amount, and the primary contact lookup on the Deal resolves to the ContactId on the corresponding Dynamics 365 Opportunity.

NextCRM custom field definitions and their values migrate alongside Contact records. We map NextCRM field types to equivalent Dynamics 365 field types: text to Single Line of Text, textarea to Multiple Lines of Text, number to Whole Number or Decimal, date to Date Only or Date and Time, checkbox to Two Options, dropdown to Option Set. We pre-create all custom fields in the Dynamics 365 target environment via the Dataverse API before any data loads so that the schema exists at migration time. Custom field API names preserve the NextCRM naming convention with an nxcrm_ prefix to avoid conflicts with standard Dynamics 365 fields.

The open-source NextCRM edition includes invoice records with series, line items, and tax engine data. These migrate to a custom Invoice entity in Microsoft Dynamics 365 Sales provisioned during migration, with lookup resolution against the parent Account and Contact. Invoice line items map to a custom Invoice Line entity with lookup to the Invoice parent. Tax configuration migrates as custom fields; Microsoft Dynamics 365 Sales does not include a native tax engine, so any tax logic is preserved as documentation for the customer's finance team to configure in their preferred tax add-on or Power Automate flow.

NextCRM Project records (open-source edition) migrate to a custom Project entity in Microsoft Dynamics 365 Sales with lookup relationships to the Account and primary Contact. Task assignments map to a custom Project Task entity with assignment owner resolution against the Dynamics 365 User table. Project status fields map to an Option Set with values (Not Started, In Progress, On Hold, Completed, Cancelled). We pre-create the custom entity schema before migration and resolve all owner references by email match against the destination Users table.