Migrate from Marketing 360 to Twenty CRM

Marketing 360 Contact records map to Twenty Person. The src fields firstName, lastName, email, phone, and contactName map to the equivalent Twenty Person fields. The Marketing 360 customerId becomes a custom identifier field for cross-system reconciliation. We run assignee and company resolution before Person insert to satisfy any lookup requirements in Twenty's schema.

Marketing 360 Contacts with a populated organizationId link to the equivalent Marketing 360 Company record. We resolve this lookup at migration time by first extracting the full Companies list, then inserting Companies into Twenty as Company records, and finally linking each Person to the corresponding Company via the workEmail.domain match or an explicit companyLink field.

Marketing 360 Company records (exposed via organizationId on Contact) map to Twenty Company. The company name, domain, address fields, phone, and any custom fields migrate as typed fields on the Twenty Company object. We create the Company records first in the migration sequence so that Person records can reference them via lookup during import.

Marketing 360 exposes custom fields via a dedicated Custom Fields API with id-value pairs per contact. Twenty requires custom fields to be pre-created in Settings → Data Model before CSV or API import. We extract the full Marketing 360 custom field taxonomy during scoping, create matching custom fields in Twenty (with appropriate types: text, number, date, select, multi-select), and then import the values as part of the Person or Company record insert. Fields must exist before import; we handle this as a pre-import configuration step.

Marketing 360 Contacts carry a tags array with id and tag name. We extract the full tag taxonomy and apply tag memberships to migrated Persons in Twenty. Depending on tag usage (segmentation versus classification), we either create a tags custom field on Person or use a separate Tag approach. The customer selects the strategy during scoping based on how tags drive their workflow in Twenty.

Marketing 360 stores assignees as username, fullName, and email nested under Contact records. We extract the distinct assignee set and match by email against Twenty workspace members. Where no matching user exists, we hold the assignee in a reconciliation queue for the customer's admin to provision the Twenty user before record import resumes. Unresolved assignees are logged with the contact record for post-migration cleanup.

Marketing 360 uses arbitrary name-id pairs for contact Statuses and Types. We extract the full taxonomy from the API and map these to equivalent custom picklist fields in Twenty Person. The picklist values are created in Twenty's Data Model during the pre-import schema setup, and the migrated Status and Type values are applied to the Person records during import.

The UXi export tool produces XML containing Posts, Pages, Testimonials, and Media. Layout files and theme assets are not included. We extract text content, categories, tags, and media URLs from the XML and deliver them as a structured export package for the customer's team to import into their chosen CMS (WordPress, Webflow, or another platform). We do not rebuild the website design or host the content ourselves.

Marketing 360 Testimonials export via the UXi XML as structured records with author name, content, and media URLs. We extract these and deliver as a CSV or JSON package that the customer's team can import into Twenty as Note records linked to the relevant Person or Company, or into a custom Testimonials object if they choose to create one.

Marketing 360 automation and journey logic—trigger conditions, time delays, branch rules, and subscriber entry points—are stored in the platform's application layer and not exposed via the public REST API. We cannot migrate automated workflows automatically. During migration scoping we document all active journeys and provide a manual rebuild checklist mapped to equivalent workflow features in Twenty CRM. The customer's team rebuilds these post-migration.