Migrate from Advantage HITS to Microsoft Dynamics 365 Sales

Discovery and extraction method agreement

We audit the Advantage HITS instance via authenticated web session, enumerating all standard objects (Contacts, Companies, Deals, Pipelines, Activities), user-defined fields, pipeline stage definitions, and active user accounts. We extract the pipeline stage definitions separately and document the stage name crosswalk. We confirm with the customer whether any custom objects or bespoke UI elements exist that need to be documented manually. We agree on the extraction method (authenticated session scraping vs any available bulk export feature) and obtain the session credentials needed for data extraction. The discovery output is a written migration scope with record counts per object, a field inventory, and the agreed extraction method.

Schema design and stage crosswalk configuration

We design the destination schema in Microsoft Microsoft Dynamics 365 Sales . This includes provisioning custom fields (with type-mapped Dataverse field types), Opportunity Record Types (one per Advantage HITS pipeline if multiple exist), and Sales Processes with stage picklist values that match the Advantage HITS stage names. The stage crosswalk is built as a mapping table that links each Advantage HITS free-text stage name to a Dynamics 365 StageName value. We deploy the schema to the destination Dynamics 365 environment via the Dataverse Web API or a sandbox first for validation. Owner reconciliation begins here: we extract all distinct owner emails and match against the destination User table, flagging any missing users for the customer's admin to provision.

Data profiling and quality remediation planning

We run a data quality profile on the extracted records, checking for missing required fields (LastName, Email), duplicate email addresses, inactive owner assignments, deals with undefined pipeline stages, and activity records with no parent record reference. We deliver a data quality report to the customer with specific record IDs and recommended actions (archive, merge, fix, or delete). The customer remediates data quality issues before migration. We do not auto-delete or auto-merge records; the customer decides on the remediation approach and we re-extract after remediation is complete.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 sandbox environment using production-like data volume. The customer's CRM lead reconciles record counts per object, spot-checks 20-30 records against the Advantage HITS source (checking field values, activity timestamps, and owner assignments), and validates the pipeline stage mapping by reviewing a sample of migrated Opportunities. Any mapping corrections, missing field additions, or stage crosswalk adjustments happen in the sandbox before production migration begins. The customer signs off on the sandbox migration before we proceed to production.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Advantage HITS Companies), Contacts (with parent AccountId resolved), Opportunities (with OwnerId, AccountId, and StageName resolved via the stage crosswalk), Activities (Tasks, Events, EmailMessages via Dataverse Bulk API with batch chunking and parent-record lookup). Each phase emits a row-count reconciliation report before the next phase begins. Owner mismatches from the reconciliation queue are resolved by the customer's admin between phases if new Users have been provisioned. Custom fields are created in the Dynamics 365 solution before the relevant object import phase if they were not available during sandbox.

Cutover, final validation, and automation rebuild handoff

We freeze Advantage HITS write access during the cutover window, 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 a cutover report with record counts per object, any records that could not be migrated with reasons, and a list of fields that carried over versus fields that could not be mapped. We deliver a written inventory of any automations, workflows, or sequences identified in Advantage HITS that require rebuild in Microsoft Dynamics 365 Sales or Power Automate. We do not rebuild these as part of the migration scope. We offer a one-week hypercare window for reconciliation issues raised by the sales team during initial Dynamics 365 usage.