Migrate from FunnelMaker to Microsoft Dynamics 365 Sales

Scoping and export method assessment

We audit the FunnelMaker account across contacts, companies, opportunities, pipelines, activities, custom objects, workflow rules, drip campaigns, and lead scoring configurations. Because FunnelMaker lacks a public API, we identify the available export path for each object type: in-product CSV for standard objects, Zapier or Make integration extracts where configured, and manual field-by-field pulls for complex custom objects. We flag any contacts approaching or exceeding the current FunnelMaker pricing tier ceiling. The scoping output is a written migration scope document specifying export method per object, estimated record counts, and any data requiring pre-migration cleanup.

Dataverse schema provisioning

We inspect FunnelMaker's full custom field inventory and create the corresponding Dataverse columns and custom tables in a pre-production Dynamics 365 environment before any data import. This includes all user-defined fields on Contact, Company, Opportunity, and custom objects mapped to their Dataverse column types. We configure Business Process Flow stages corresponding to each FunnelMaker pipeline, set stage probabilities, and define the Lead-versus-Contact split rule based on the customer's FunnelMaker lifecycle model. Schema is deployed via the Dataverse Web API into a Sandbox environment for validation before production migration.

CSV extraction and data quality remediation

We work with the customer to extract FunnelMaker data via available CSV exports and Zapier integrations. Any records with missing required fields for Dynamics 365 (such as Contact records without a parent Account reference) are flagged in a data quality report. We clean dedupe keys, normalize date formats, validate email address syntax, and resolve orphaned records before transformation. Data quality issues are the most common cause of Dataverse upsert failures, so we allocate remediation time per the scoping findings.

Sandbox migration and reconciliation

We run a full migration into the Dynamics 365 Sandbox environment using production-like data volume. The customer's sales operations lead reconciles record counts across all object types, spot-checks a sample of migrated records against the FunnelMaker source, and validates pipeline stage assignments and custom field values. Any mapping corrections are applied before production migration begins. This step catches schema mismatches and transformation errors at zero risk to production data.

Owner and user provisioning coordination

We extract every distinct FunnelMaker Owner referenced on records and match by email against the Dynamics 365 User table. Owners without a matching Dynamics 365 User go to a reconciliation queue. The customer's Dynamics 365 admin provisions any missing Users before the production migration phase begins. OwnerId references must be resolved before Opportunity and Activity records can be imported because Dynamics 365 enforces referential integrity on the Owner field.

Production migration in dependency order

We run production migration in record-dependency order: Accounts (from FunnelMaker Companies), Leads and Contacts (with the lifecycle split applied and AccountId resolved), Opportunities (with AccountId, OwnerId, and Business Process Flow stage resolved), Activity history (Tasks and Emails via Dataverse Bulk API with chunking and backoff), Custom Objects (with Dataverse lookups to parent records resolved), and Tags/Groups (as marketing list memberships or custom columns). Each phase emits a row-count reconciliation report before the next phase begins. Call recording audio files and transcription text are excluded as documented.

Cutover, validation, and workflow rebuild handoff

We freeze FunnelMaker writes during cutover, run a final delta migration of any records modified during the migration window, then set Microsoft Dynamics 365 Sales as the system of record. We deliver the workflow and drip campaign inventory document to the customer's admin team with recommended Power Automate equivalents. We support a one-week post-cutover window to resolve reconciliation issues. We do not rebuild FunnelMaker Workflows or drip campaigns as Power Automate flows inside the migration scope; that is a separate engagement.