Migrate from Marketing 360 to Nutshell

Marketing 360 Contact records map to Nutshell Person. We extract id, firstName, lastName, email, phone, contactName, and customerId via paginated API reads, then map each to Nutshell's Person fields. Email serves as the dedupe key during import. Custom field values transfer to pre-created Nutshell custom fields. Note that Nutshell custom fields must be created in the Nutshell UI before migration begins because Nutshell enforces type restrictions that differ from Marketing 360's schema.

Marketing 360 does not have a native Company object, but Contact records carry an organizationId field that we use to reconstruct Company records in Nutshell. We group Contacts by organizationId, extract organization-level details where available, and create one Nutshell Company per unique organizationId. The Nutshell Company serves as the parent for all related Person records.

Marketing 360 exposes a Custom Fields API with id-value pairs per contact. We map these to Nutshell custom fields, but Nutshell custom fields have type restrictions (no date-only format, no multi-select text) that require type coercion during import. We pre-create all Nutshell custom fields in the UI before migration, validate field types, and apply transformation logic for any incompatible source field types.

Marketing 360 Contact records carry tag arrays with id and tag name. We extract the full tag taxonomy from the source API, deduplicate tag names, and apply tag memberships to migrated Nutshell Person records. Tags used for segmentation in Marketing 360 journeys become standard Nutshell tags for manual segmentation. Active journey-triggered tags cannot migrate because the journey logic does not transfer.

Marketing 360 stores assignees as nested username, fullName, and email under each Contact. We extract all distinct assignee emails and match them against Nutshell User accounts by email. Any assignee without a matching Nutshell User is held in a reconciliation queue for the customer's admin to provision before Person import resumes. Unassigned Contacts default to a migration service account temporarily and are reassigned post-migration.

Marketing 360 uses arbitrary name-id pairs for Contact Statuses and Types. We extract the full taxonomy from the API and map these to Nutshell Person custom fields (text or picklist) since Nutshell does not have native Status or Type objects. The customer chooses the destination field names during scoping, and we document the mapping so the admin can validate label alignment post-migration.

Marketing 360 engagement records (calls, emails, meetings, tasks, notes) migrate to Nutshell Activity records linked to the corresponding Person or Company. We resolve the Person parent reference at migration time using the email dedupe key. Activity timestamps preserve to maintain the historical timeline. Note that Marketing 360 email content and attachments migrate only if accessible via the API; embedded images and attachments require separate download-and-reupload handling.

Marketing 360 Testimonials export via UXi XML as structured records with author name, content, and media URLs. Nutshell does not have a native Testimonials object, so we import testimonials as Note records attached to the relevant Person or Company, or as file Attachments if the customer prefers a cleaner separation. We flag this as a configuration choice during scoping.