Migrate from InTouch CRM to Microsoft Dynamics 365 Sales

Discovery and InTouch CRM export scoping

We audit the InTouch CRM instance to identify the full record set across Contacts, Companies, Deals, Activities, and any custom fields or pipeline configurations. We assess the InTouch CRM export utility to confirm CSV export capability, pagination limits, and whether historical timestamps are preserved in the output. We pair this with a Microsoft Dynamics 365 Sales edition review (Sales Starter, Sales Professional, Sales Enterprise) to determine which features the target org includes. The discovery output is a written migration scope document with record counts, pipeline stage inventory, and a decision checklist for stage remapping.

Destination schema design and validation rule audit

We design the Microsoft Dynamics 365 Sales target schema: Account and Contact fields from the Company and Contact mappings, Opportunity Record Types and Sales Processes from the Pipeline mapping, and custom fields for InTouch CRM custom fields and the intouch_deal_id__c audit field. We audit existing validation rules, field-level security, and required-field configurations in the target Dynamics 365 org and document which rules require temporary disabling or extension during migration. Schema is deployed into a Sandbox org first for validation.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox (Full Copy or Partial Copy) using production-like data volume extracted from InTouch CRM. The customer's admin reconciles record counts (Accounts in, Contacts in, Opportunities in, Activities in), spot-checks 25-50 records against the InTouch CRM source, and approves the schema and mapping before production migration begins. Any mapping corrections happen here, not in production.

Owner reconciliation and User provisioning

We extract every distinct InTouch CRM Owner referenced on Contacts, Companies, Deals, and Activities and match by email against the Dynamics 365 destination org's User table. Owners without a matching User go to a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users before record import resumes. OwnerId references must be resolved before any standard object insert because Dynamics 365 enforces ownership on most standard entities.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from InTouch Companies), Contacts (with AccountId resolved to the parent Account), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Activity history (Tasks, Events via Bulk API with batch chunking and parent-record resolution). Each phase emits a row-count reconciliation report before the next phase begins. We implement exponential backoff on Bulk API calls to handle Dynamics 365 service protection limits gracefully.

Cutover, validation, and automation rebuild handoff

We freeze InTouch CRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Microsoft Dynamics 365 Sales as the system of record. We deliver the automation and workflow inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues. We do not rebuild InTouch CRM automations as Dynamics 365 Flow or Power Automate inside the migration scope; that is a separate engagement or an internal admin task.