Migrate from Factoreal to Microsoft Dynamics 365 Sales

Discovery and export request

We audit the Factoreal account across contacts, segments, campaigns, automation list, email templates, e-commerce orders, tags, and custom fields. We request a full CSV data export from the Factoreal application early in the project so the customer can review the data shape before migration begins. We document the segment filter logic, automation workflow graph, and any known data quality issues flagged during the export process. The discovery output is a written migration scope and a custom entity schema design for Dynamics 365 Dataverse if e-commerce or order data is in scope.

CSV preprocessing and data quality

We run all Factoreal CSV exports through a preprocessing pipeline that deduplicates records, validates required field presence for Dynamics 365 import, normalizes character encoding, and splits the contact list into Account-Contact and Lead segments based on company association. Preprocessing emits a data quality report listing record counts by status (clean, deduplicated, flagged for manual review) so the customer can make informed decisions about records that require manual correction before import.

Dynamics 365 schema preparation

We create the target schema in Dynamics 365 Dataverse before any data import. This includes custom fields on Contact and Account for Factoreal lifecycle data and original record IDs, custom fields on Lead for source attribution, custom entities for e-commerce order and line item data if in scope, and the segment or static list configuration in Dynamics 365 Marketing if marketing lists are used. Schema is deployed to a Dynamics 365 Sandbox environment first for validation.

Sandbox migration and reconciliation

We run a full migration into a Dynamics 365 Sandbox using production-like data volume. The customer reconciles record counts (Contacts in, Leads in, Accounts in, Campaigns in, Activities in), spot-checks 25-50 records against the Factoreal source, and reviews segment membership in Dynamics 365. Any mapping corrections happen in the sandbox phase. Sign-off on the sandbox migration is required before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from Factoreal company associations), Contacts (with AccountId resolved), Leads (unassociated Factoreal contacts), Campaigns, Campaign Members (segment membership reconstructed as Lists or dynamic groups), Email Templates, Activities (email, SMS, WhatsApp logs via Dataverse API), e-commerce order data (custom Dataverse entities), and Tags (mapped to custom fields or Topics). Each phase emits a row-count reconciliation report before the next phase begins.

Cutover, validation, and automation handoff

We freeze Factoreal writes during cutover and run a final delta migration of any records modified during the migration window. We enable Dynamics 365 as the system of record and deliver the automation workflow inventory document to the customer's Dynamics admin for rebuild in Power Automate or Dynamics Sales automation. We support a one-week hypercare window where we resolve reconciliation issues. Post-cutover workflow rebuild, Power Automate configuration, and Dynamics 365 admin training are outside standard migration scope and are quoted separately.