Migrate from AdOrbit to Nutshell

Discovery and data audit

We audit the source AdOrbit account to establish record counts for Contacts, Companies, Ad Tickets, Orders, Subscriptions, Freelancers, and any custom objects or ticket fields in use. We review the AdOrbit plan tier (Starter, Professional, Enterprise) to understand which features are active and whether the Freelancer Management module and Accounts Receivables module are enabled. We extract the custom field schema (ticket type taxonomies, custom contact properties, order line item fields) and review any active Automation Workflows. The discovery output is a written scope document that includes the record count per object, the custom field schema list, and the workflow inventory requiring rebuild.

Schema design for Nutshell custom fields

We design the Nutshell custom field schema based on the AdOrbit custom field audit. This includes creating custom fields on Contact (for subscription and freelancer properties), on Company (for company type and industry mapping), and on Deal (for Ad Ticket fields such as ticket type, publication, issue date, ad size, placement, rate, and pricing model). We create the custom picklist option sets to match AdOrbit's ticket type and order status values. Nutshell's custom field creation happens in the account settings before any data import begins; we coordinate with the customer's Nutshell admin to apply these changes.

CSV extraction, sanitization, and reformatting

We extract data from AdOrbit via the REST API or CSV export. Every exported CSV is sanitized: embedded commas in text fields are replaced with semicolons, date formats are normalized to the format Nutshell's import wizard expects, and multi-select or freeform fields are split into separate columns if required. We reformat the column headers to match Nutshell's expected field names. The sanitized CSVs are validated against a row-count reconciliation before upload.

Company and Contact import

We import AdOrbit Companies first, using the company name as the dedupe key. Companies are created with the company type custom field populated from AdOrbit. We then import Contacts with the company reference resolved by matching the contact's company name or domain to the imported Company record. Owner references are resolved by email against the Nutshell User table; unresolved owners are held for admin provisioning before we proceed.

Deal import from Ad Orders and Ad Tickets

We import AdOrbit Orders as Nutshell Deals, mapping the order status to the Nutshell Deal status and populating the custom Ad Ticket fields (ticket type, publication, issue date, ad size, rate, pricing model) on the Deal. CPM-based orders have the flat amount computed from CPM rate and quantity and stored as Deal Amount, with the original CPM rate preserved in a custom field. We attach any Ad Ticket files and PDFs to the corresponding Deal record.

Subscription, Freelancer, and remaining object import

AdOrbit Subscriptions migrate as Contacts with subscription properties in custom fields. Freelancer records migrate as Contacts with a freelancer type classification. Open balances and tax codes are flagged as reconciliation items and noted in the migration report. Any media inventory exports from AdOrbit are transferred as files or mapped to a custom object or Deal-linked records per the customer's preference.

Cutover, validation, and workflow handoff

We freeze AdOrbit writes during the cutover window, run a final delta migration of any records modified during the migration, then mark Nutshell as the system of record. We validate record counts against the discovery baseline and spot-check 25-50 records per object for field-level accuracy. We deliver the Automation Workflow inventory document and the mapping notes for each workflow's recommended Nutshell equivalent. We support a 5-day hypercare window for reconciliation issues. We do not rebuild AdOrbit workflows as Nutshell automations inside the migration scope; that is a separate engagement.