Migrate from BenchmarkONE to Microsoft Dynamics 365 Sales

Discovery and scoping

We audit the BenchmarkONE account across tier (Free, Lite, Pro), record counts by object type, custom field definitions, active automations, engagement volume, and email campaign history. We pair this with a Dynamics 365 edition recommendation: Sales Professional ($65/user) covers most BenchmarkONE migrations with no custom objects; Sales Enterprise ($105/user) is required if the customer needs multiple sales processes, advanced forecasting, or Power Platform access. We also assess the Lead-Contact split candidate set and flag the Temperature field for custom field creation.

Schema design and Lead-Contact split rule

We design the Dynamics 365 destination schema in a Sandbox environment before touching production. This includes creating the Temperature custom field on Lead and Contact, configuring Account-Contact hierarchy settings, setting up Opportunity stages mapped from BenchmarkONE Deal stages, defining Record Types per BenchmarkONE pipeline if multiple pipelines exist, provisioning Multi-Select Picklists or Topics for tag migration, and writing the Lead-Contact split rule based on the customer's Contact Status and Temperature values. The rule is validated against a sample of 50-100 source records before finalizing.

Data quality audit and preparation

We run a pre-flight data quality audit on the BenchmarkONE export. This includes duplicate detection across name and email, address completeness check, required-field validation against the Dynamics 365 target schema, phone and date format standardization, and contact status normalization. We produce a data quality report listing records that require remediation before import. Remediation is a shared task: the customer cleans source records, or we apply transforms during the migration load.

Admin-only extraction from BenchmarkONE

We coordinate with the customer to confirm admin-level access to BenchmarkONE's full database export (Account Settings > Data > Export Data). Only System Administrators can trigger this export; non-admin users cannot access it. We extract the full dataset including Contacts, Companies, Deals, Tasks, Tags, Custom Fields, Email Campaigns, and Social Profiles. We cross-validate record counts from the CSV export against API query results to confirm completeness before transformation begins.

Sandbox test migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox using production-like data volume. The customer's RevOps lead or admin reconciles record counts against the BenchmarkONE source (Contacts in, Leads and Contacts out; Companies in, Accounts out; Deals in, Opportunities out), spot-checks 25-50 records for field-level accuracy, and validates that the Lead-Contact split rule applied correctly. Any mapping corrections are made in the transformation layer before production migration begins. Sign-off on the sandbox reconciliation gates the production migration start.

Production migration in dependency order

We run the production migration in record-dependency order: Accounts (from Companies), Leads (with split rule applied), Contacts (with AccountId resolved), Opportunities (with AccountId, OwnerId, and RecordTypeId resolved), Tasks (with OwnerId resolved via User mapping), Engagement history (emails, calls, meetings as Activity records via Dynamics 365 API with chunking and backoff), Tags (as Multi-Select Picklist or Topics per the chosen strategy), and Custom Fields last. Each phase emits a row-count reconciliation report before the next phase begins. Any record rejected by Dynamics 365 validation is logged, remediated, and retried in the same phase.

Cutover, validation, and automation rebuild handoff

We freeze writes in BenchmarkONE during cutover, run a final delta migration of any records modified during the migration window, then enable Dynamics 365 as the system of record. We validate final record counts and spot-check 25-50 records against the source. We deliver the BenchmarkONE automation inventory and Power Automate rebuild guide as a written handoff document. We support a one-week hypercare window for reconciliation issues raised by the customer's sales team. Power Automate workflow rebuild and Dynamics 365 Marketing provisioning are separate engagements outside standard migration scope.