Migrate from RSoft CRM to Microsoft Dynamics 365 Sales

Discovery and RSoft plan audit

We audit the source RSoft account for plan tier (Standard/Advanced/Enterprise/Customised), total record counts per object, active add-ons (IVR, WhatsApp, autodialer), custom field names, pipeline count, and automation scope. We extract a sample CSV to validate field headers, data types, and export completeness. We identify IVR and WhatsApp module gaps during this step and scope file transfer separately. The discovery output is a written migration scope including record counts, field mapping draft, and a Microsoft Dynamics 365 Sales edition recommendation based on the customer's user count and feature requirements.

Export sequencing and data quality profile

We guide the customer through a structured CSV export from RSoft in record-dependency order: Companies first, then Contacts, then Leads, then Deals, then Activities, then Tickets. We run a data quality profile on each CSV (null rates, duplicate email counts, malformed dates, orphaned foreign keys) and surface type mismatches before any Dynamics insert. Any RSoft export that was already completed out of order triggers a re-export request to ensure Account records exist before Contact insert.

Dynamics 365 schema setup

We create the destination Microsoft Dynamics 365 Sales schema in a Sandbox environment. This includes custom fields on Account, Contact, Lead, Opportunity, and Case entities matching the RSoft custom field names and types. We configure Sales Processes and stage definitions mapping RSoft pipeline stages to Dynamics Opportunity stages with correct probabilities. We provision the migration user's security role and Bulk API permissions, and temporarily disable validation rules and duplicate detection rules that could block bulk insert.

Sandbox migration and reconciliation

We run a full migration into Dynamics Sandbox using production-like data volume. The customer's RevOps lead reviews record counts (Accounts in, Contacts in, Leads in, Opportunities in, Activities in), spot-checks 20-30 random records against the RSoft source, and validates that parent-child relationships (Contact to Account, Opportunity to Account and Contact) are intact. Any field mapping corrections, picklist value gaps, or validation rule failures surface here before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from RSoft Companies), Contacts (with AccountId resolved), Leads (owner resolved by email), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Activities (via Dynamics Bulk API in 1,000-record batches with RegardingObjectId resolution), Cases (from RSoft Tickets), and Tags (as native Dynamics Tags or custom fields). Each phase emits a row-count reconciliation report. We flag and hold any record with an unresolved Owner or Account lookup for the customer to remediate before proceeding.

Cutover, validation, and automation rebuild handoff

We freeze writes in RSoft during cutover and run a final delta migration for any records modified during the migration window. We validate final record counts against discovery estimates and deliver the RSoft Workflow and Automation inventory document to the customer's admin team for rebuild in Microsoft Dynamics 365 Sales Power Automate or Dynamics workflows. We support a one-week hypercare window for reconciliation issues. We do not rebuild RSoft Automations as Dynamics workflows inside migration scope; that is a separate engagement.