Migrate from Grow CRM to Microsoft Dynamics 365 Sales

Grow CRM's Contact object holds all person records including those that would be classified as Leads in Microsoft Dynamics 365 Sales . We split contacts at migration time using Grow CRM's contact status field: contacts with status 'Lead' or no pipeline assignment map to Salesforce Lead; contacts attached to a Grow CRM Company or Opportunity map to Dynamics 365 Contact linked to an Account. The original Grow CRM contact status is preserved in a custom field gcl_crm_status__c on both Lead and Contact for audit and reporting continuity.

Grow CRM Company records map directly to Microsoft Microsoft Dynamics 365 Sales Account. Company name becomes the Account Name field, and the website domain is mapped to Account Website. We use company name as the dedupe key during import. Account is inserted before Contact to satisfy the parent AccountId lookup that attaches Contacts to the business entity.

Grow CRM Lead records (a distinct object from Contact in Grow CRM) map directly to Microsoft Microsoft Dynamics 365 Sales Lead. Lead status, source, and owner assignment fields migrate to their Dynamics equivalents. Any Grow CRM lead score value is preserved in a custom field gcl_lead_score__c on the Dynamics Lead.

Grow CRM Opportunity records map to Microsoft Dynamics 365 Sales Opportunity. The pipeline stage name from Grow CRM is mapped to a Microsoft Dynamics 365 Sales Process stage value, and the pipeline identifier maps to a Record Type. Deal value, expected close date, probability (if set in Grow CRM), owner assignment, and the linked Contact and Company all transfer. Grow CRM's pipeline stage order is preserved by configuring the Sales Process stage sequence before migration runs.

Grow CRM Task records migrate to Microsoft Dynamics 365 Sales Task. Task title, description, due date, status, priority, and owner assignment transfer directly. Grow CRM custom fields on Tasks require schema extraction from the source instance during scoping; we pre-create matching custom fields in Dynamics 365 before the Task import batch. Task assignment resolves the Grow CRM owner to a Dynamics 365 User by email match.

Grow CRM Invoices with line items, totals, tax, payment status, and client linkage migrate to Microsoft Dynamics 365 Sales Order records in the base tier, or to a custom Invoice entity built in Dataverse if the customer needs full invoice history preserved as a read-only record. Historical paid invoices are migrated as closed Orders; open invoices are migrated as open Orders awaiting fulfillment. The client Contact linkage is resolved at import time via the Contact-to-Account mapping.

Grow CRM Estimates (quotes with line items, validity dates, and status) map to Microsoft Microsoft Dynamics 365 Sales Quote. Quote status, expiration date, total amount, and line items transfer. If the customer has licensed Dynamics 365 Business Central alongside Sales, Quotes can be linked to Sales Orders for a full quote-to-cash flow. We flag this configuration decision during scoping.

Grow CRM Help Desk Ticket records migrate to Microsoft Microsoft Dynamics 365 Sales Case (or Dynamics 365 Customer Service Case if the customer has licensed that module). Ticket priority, status, assignee, and conversation history transfer. Ticket conversation threads are exported from Grow CRM as plain text and imported as a Note or EmailMessage record attached to the Case for a complete support history.

Grow CRM tags on Contacts, Companies, and Opportunities are stored as comma-separated values or array fields in the export. We normalise tag values during the transform step and write them to a custom multi-select picklist field gcl_tags__c on the corresponding Dynamics 365 object. The customer chooses during scoping whether tags should be preserved as a flat multi-select or consolidated into a subset of meaningful values to keep the picklist manageable.

Grow CRM custom fields on Tasks and Clients (the only objects that support custom fields in Grow CRM) are not included in the standard CSV export. We extract the field definitions — name, data type, and option values — from the Grow CRM UI or database during scoping and document them as a schema specification. We pre-create matching custom fields in Dynamics 365 before the data import runs, preventing import failures caused by missing target fields. This step is manual and required before any import batch begins.

Grow CRM team member records map to Microsoft Microsoft Dynamics 365 Sales User by email address. We extract every distinct owner referenced on Contacts, Companies, Opportunities, Tasks, and Tickets and match against the destination User table. Any Grow CRM owner without a matching Dynamics 365 User is placed in a reconciliation queue and the customer's admin provisions the missing User before the relevant import phase resumes.