Migrate from Marketing Tools Growth Marketing Platform to Nutshell

Standard Contact fields (name, email, phone, address, company linkage) export cleanly from the source platform via REST API. We map them directly to Nutshell Contact records using email as the dedupe key, splitting bulk exports into batches of no more than 5,000 records per call to avoid the UI timeout issue that affects large-volume imports. Company linkage is resolved by cross-referencing the source's contact-company pairs against the Account records created in the prior mapping phase.

Company records export as part of the standard contact export with contact-company linkage preserved. We extract Company records as a distinct set, map them to Nutshell Accounts, and re-establish the Contact-to-Account relationship at import time using domain-based matching or explicit company_id cross-reference. Accounts are migrated before Contacts so the lookup relationship is satisfied on insert.

Segment definitions on the source platform are rule-based with platform-specific syntax that is not exportable. We extract per-contact segment membership during the discovery phase, producing a contact-email-to-segment membership matrix. Each source segment becomes a static Nutshell List, and we create List Membership records linking each Contact to its applicable Lists. The underlying rule logic must be rebuilt in Nutshell's filtered Views or manually managed Lists by the customer's admin.

Campaign metadata — name, status, start date, end date, and channel — exports from the source platform and maps directly to Nutshell Campaign records. We do not migrate campaign performance metrics (open rates, click rates, revenue attribution) because they are not available via the standard export path. We advise customers to export reporting snapshots from the source analytics dashboard before cutover and preserve them as a reference CSV.

Tags export as flat key-value pairs per contact. We map them directly to Nutshell's tag field, using the tag name as the matching key. We flag any tags that exceed Nutshell's character limits before import and surface them to the customer for renaming or truncation.

Custom object schema on the source platform is not publicly documented in the available evidence base. Where customers report custom object usage, we attempt field-level mapping during the scoping call by querying the source API's dynamic schema endpoint and comparing against Nutshell's custom field model. If a custom object has a direct 1:1 relationship to Contacts or Accounts, we map it to a custom field. If it is a standalone entity, we document the schema gap and recommend a post-migration custom object implementation plan. Schema discovery is scoped as a billable pre-migration task if the customer has more than three custom object types.

File attachments associated with contacts or campaigns are not available via the documented export path on the source platform. Customers should export attachments separately via the platform's UI export feature before the cutover date. We do not attempt to script a workaround for undocumented export endpoints as part of standard migration scope.

Workflow journey definitions — triggers, conditions, branch logic, and action steps — live in the platform's internal automation engine and are not accessible via export. We cannot carry them over automatically. During discovery we document every active journey, capture screenshots of the flow, and produce a written rebuild guide mapped to Nutshell's workflow rules and Tasks. The customer's admin rebuilds journeys in Nutshell within the first migration sprint.