Migrate from Genoo to Microsoft Dynamics 365 Sales

Discovery and export planning

We audit the Genoo account through the manual export UI, extracting record counts across Leads, Contacts, Accounts, Campaigns, Campaign members, Event registrations, and Form submissions. We identify the customer's Genoo feature set (which features are active) and map each to a destination object in Dynamics. We also document landing page and email template configurations, content library file references, and lead scoring rules during discovery. The output is a written migration scope, a list of export batches required from Genoo's UI, and a list of items that require manual handling (assets, scoring logic, landing pages) that will be delivered as written inventories.

Destination schema design

We design the Microsoft Dynamics 365 Sales schema based on the scoping output. This includes creating custom fields on Lead and Contact (genoo_lead_source__c, genoo_original_lifecycle_stage__c, genoo_form_submission__c), provisioning a custom Form Submission entity if form field responses require preservation, and configuring the Account-Contact relationship model. We deploy schema to a Dynamics Sandbox (Full Copy or Partial Copy) first for validation. If the customer uses Microsoft Dynamics 365 Sales Enterprise or Premium, we also configure Sales Process stages, Record Types, and Page Layouts during this phase.

Export extraction and relationship reconciliation

We work with the customer to execute multiple scoped exports from Genoo's manual export UI: Leads, Contacts, Accounts, Campaigns, Campaign members, and Event registrations in separate batches. We reconcile relationships by email address as the join key — matching Campaign members to migrated Leads, matching Contacts to Accounts, and flagging any email addresses that appear across multiple object types. The reconciliation output is a relationship map that guides the insert-order sequence in Dynamics. We also generate the content library asset manifest during this phase and hand it to the customer for manual download.

Sandbox migration and validation

We run a full migration into the Dynamics Sandbox using production-like data volume. The customer's Dynamics admin or RevOps lead reconciles record counts (Accounts in, Contacts in, Leads in, Campaign members in, Activities in), spot-checks 20-30 records against the Genoo source data, and validates that the Account-Contact lookup chain is intact (no orphaned Contacts without a parent Account). The sandbox validation must be signed off before production migration begins. Any mapping corrections — field type mismatches, picklist value gaps, missing required fields — happen here, not in production.

Owner reconciliation and User provisioning

We extract every distinct Genoo owner referenced in the export data and match by email address against the Dynamics destination org's User table. Owners without a matching Dynamics User go to a reconciliation queue. The customer's Dynamics admin provisions any missing Users (active or inactive depending on whether the original Genoo user is still active). Migration cannot proceed past this step because OwnerId references are required on Leads, Contacts, and Opportunities in Dynamics. We also validate that the migration user's security role grants the necessary permissions for create, read, update, and bulk insert operations.

Production migration in dependency order

We run production migration in record-dependency order: Accounts first (from Genoo Accounts), then Contacts (with AccountId resolved from the Account load), then Leads, then Campaigns, then CampaignMember records (with LeadId resolved from the Lead load), then Event registrations and Form submissions as custom entities or Notes. Each phase emits a row-count reconciliation report before the next phase begins. We use the Dynamics Dataverse REST API with batch chunking and exponential backoff on rate limit responses. We do not use Dynamics Data Loader for large volumes because it does not handle complex parent-record resolution.

Cutover, validation, and inventory handoff

We freeze Genoo 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 validate that all Contact records have a parent Account and that CampaignMember counts match the exported Campaign membership totals. We deliver the written inventory documents: lead scoring configuration for rebuild, content library asset manifest for re-upload, landing page and email template inventory for rebuild in the customer's chosen tool. We support a five-business-day hypercare window where we resolve any data quality issues raised by the customer's sales team. Workflows, automations, and marketing sequences do not migrate and are not rebuilt within the migration scope.