Migrate from Ontraport to Nutshell

Ontraport Contact records map directly to Nutshell People. All standard fields (First Name, Last Name, Email, Phone, Address) migrate 1:1. Custom fields migrate as custom fields on Nutshell People, with type mapping from Ontraport field types (text, number, date, dropdown, checkbox) to equivalent Nutshell field types. Lifecycle stage and source data from Ontraport preserve as custom fields on the Person record for reporting continuity. The Ontraport contact's primary email address becomes the Person email; we flag duplicates during import using Nutshell's dedupe matching on email.

Ontraport Company records map to Nutshell Accounts. The Company name becomes the Account name, and domain data maps to the Account website field. We recommend deduping Company names before import since Ontraport does not enforce name uniqueness; identical companies with different Ontraport IDs will create duplicate Nutshell Accounts unless deduped upstream. The Account is created before any linked Person import so that the Account-Person relationship is satisfied at import time.

Ontraport Deal records map to Nutshell Opportunities. The Deal pipeline maps to a Nutshell Pipeline that we pre-configure before migration, with stages mapped to Nutshell stage values. Deal amount, close date, owner assignment, and Contact or Company associations migrate directly. Pipeline IDs in Ontraport are destination-specific; we configure matching Nutshell pipelines during the setup phase and map Deal pipeline references to the new Nutshell pipeline IDs.

Ontraport Tags are plain-text labels applied to Contacts. We export all tag assignments per Contact and reapply them as flat tag lists at the destination. Nutshell supports tags on People, Accounts, and Opportunities. The customer chooses during scoping whether tags remain on Person only or are also applied to the linked Account. Tag migration is straightforward but requires pre-configuration of the target Nutshell tag list before record import begins.

Ontraport Notes are linked to Contact records. When exported as CSV, each Note generates a separate row duplicating the full Contact record, so we deduplicate rows after export and re-link each Note to its single Person record before Nutshell import. The Note content, author, and creation date migrate as a Note attached to the corresponding Nutshell Person.

Ontraport engagement history (calls, emails, meetings, tasks) migrates to Nutshell Activities linked to the corresponding Person, Account, or Opportunity. Activity timestamps preserve the original Ontraport engagement date for timeline ordering. Nutshell's activity model does not support bulk API import on non-Enterprise plans; we use Nutshell's CSV import flow for activity records when API access is not available, which requires manual file preparation steps. Engagement type (call, email, meeting) maps to Nutshell activity category.

Ontraport Automation Rules are stored in a proprietary format that cannot be exported or imported into any platform. We extract trigger definitions and the list of enrolled Contacts as a written inventory document that the customer's admin uses to rebuild equivalent automation logic in Nutshell. The rebuild is out of scope for the migration engagement. Automation Rules covering pipeline stage changes map more directly to Nutshell workflow triggers than complex contact journey automations.

Ontraport invoice and payment records include line items, payment status, and product associations. We export transaction history with Contact linkage and payment status for reconciliation. Nutshell does not have a native billing or invoicing module; transactions are recorded as deal-linked Activity entries or stored as custom fields on the Opportunity. We document the mapping strategy during scoping based on the customer's reporting needs.