Migrate from Ontraport to Microsoft Dynamics 365 Sales

Ontraport Contacts with lifecycle stage values indicating qualified buyers (customer, evangelist) map to Dynamics 365 Contact. Contacts with unqualified stages (subscriber, lead) map to Lead. The original Ontraport lifecycle stage migrates to a custom field on both Lead and Contact for audit. We apply the split rule during the transform phase and resolve Account lookups for all Contact records before insert.

Ontraport Company records map to Dynamics 365 Account. Company name becomes Account Name, and domain data maps to Website. Ontraport does not enforce Company dedup, so we flag duplicate Account names during scoping and recommend a dedup pass before Account insert to avoid creating duplicate Accounts in Dynamics.

Ontraport Deal records map to Dynamics 365 Opportunity. Pipeline assignment maps to a Dynamics Record Type and Sales Process. Deal stage maps to StageName with probability percentages mapped to StageProbability. Amount, close date, owner, and Contact/Company association migrate directly. Opportunity is created after Account and Contact so that parent lookups resolve at insert time.

Each Ontraport deal pipeline becomes a Dynamics 365 Record Type on Opportunity with a corresponding Sales Process that whitelists the stage values. Probability percentages transfer from Ontraport with rounding to Dynamics-allowed integer values. The customer reviews stage mapping in a sandbox before production migration.

Ontraport tags stored as text values per Contact migrate to a Dynamics multi-select picklist field. If tag volume exceeds picklist value limits (500 values), we recommend migrating to Topics with TopicAssignment records or a custom entity for tag inventory. The customer selects the strategy during scoping.

Ontraport Notes export generates duplicate Contact rows per Note (one row per Note attached to a Contact). We deduplicate these rows at transform, keeping a single Contact row with all Notes aggregated, then insert each Note as a separate Dynamics Note record linked via ContentDocumentLink to the parent Contact, Lead, or Account. This is a known Ontraport export artifact we handle without requiring manual pre-processing.

Ontraport Campaign records (email and multi-channel marketing campaigns) migrate to Dynamics 365 Campaign with campaign type, status, and target audience data. Contact and Company memberships migrate as CampaignMember records linking the Contact or Lead to the Campaign. Campaign-level configuration (sending rules, A/B testing setups) does not migrate; we inventory the campaign structure and deliver it as a rebuild reference.

Ontraport Automation Rules are stored in a proprietary format that cannot be exported as structured data. We extract trigger definitions, enrolled Contact lists, and action summaries from Ontraport's UI and API, then deliver a written inventory documenting each automation's trigger, conditions, steps, and a recommended Power Automate equivalent. The customer or a Dynamics partner rebuilds the flows post-migration.

Ontraport invoice records with line items, payment status, and product associations migrate to a custom Invoice entity in Dynamics 365 or to a SharePoint document library with invoice metadata linked to the Account and Contact. Payment status (paid, pending, failed) migrates as a custom field. Actual invoice PDFs are exported as documents and attached to the related Account or Contact record. Microsoft Dynamics 365 Sales does not have native billing; invoice records require a custom solution or third-party integration.

Ontraport custom objects (Pets, Courses, Subscriptions, etc.) with custom fields and Contact or Company relationships migrate to Dataverse custom entities. We pre-create the destination schema including all custom fields, lookup relationships, and any validation rules before data import. Contact lookups resolve via the Contact mapping already completed.

Ontraport Membership and Course content (titles, descriptions, subscriber lists, enrollment dates) migrates to a custom enrollment entity in Dynamics with the Contact lookup. Course content itself (HTML pages, video assets) requires separate export from Ontraport and re-hosting at the destination, which we flag as a content migration scope separate from the CRM data migration.