Migrate from Marketing Tools Growth Marketing Platform to Twenty CRM

Marketing Tools Growth Marketing Platform Contact records map to Twenty Person records via a 1:1 field mapping. Standard fields (name, email, phone, company linkage) export cleanly via the platform's API. We resolve the contact-to-company relationship at import time by exporting contact-company pairs and setting the Person's company linked account during the Person insert phase. Any HubSpot owner email is resolved against the Twenty User table by email match.

Marketing Tools Growth Marketing Platform Company records map to Twenty Company records. The source domain field maps to the Company website field and acts as the dedupe key during import. Twenty's Company object currently has a minimal standard field set; industry, employee count range, annual revenue, and social profile fields do not exist by default and must be created as custom fields via the Twenty Metadata API before the Company import phase begins.

Marketing Tools Growth Marketing Platform Deals map to Twenty Opportunity records. The Deal stage maps to a Twenty Opportunity status field; if the destination workspace uses custom status values, we configure those via the Metadata API before import. Deal amount, close date, and owner information migrate directly. We resolve the Opportunity's linked Company and Person at migration time via the contact-company pairs extracted during discovery.

Marketing Tools Growth Marketing Platform segment definitions are rule-based and platform-specific in syntax; the underlying rule logic cannot be exported. We extract the membership per contact (which contacts belong to which segments) and replicate that as a tag-style field on the Twenty Person record. The original segment name is preserved as a reference field so that the customer can rebuild the segment rule logic in Twenty or an external segmentation tool post-migration.

Campaign metadata (name, status, start/end dates, channel) exports from the platform. We import campaign metadata as Opportunity records with a campaign_type field set to distinguish them from deal-based opportunities, or we create a custom Campaign object via the Metadata API if the customer's campaign volume warrants it. Campaign performance metrics (open rates, click rates, attribution) are not available via standard export and are preserved as a separate reference CSV exported from the platform's analytics dashboard before cutover.

Workflow Journey definitions — triggers, conditions, branches, and action steps — live in the platform's internal automation engine and are not accessible via export. We cannot carry them over automatically. We document every active journey during the discovery call: we capture screenshots, list the trigger conditions, describe the branch logic, and note the action steps. This documented inventory is handed off to the customer's admin team with a recommendation to rebuild using Twenty's API-based workflow approach or an external automation tool within the first post-migration sprint.

Marketing Tools Growth Marketing Platform Custom Object schema is not publicly documented in the available evidence base. During discovery, we attempt field-level mapping by querying the platform's live schema where accessible and by interviewing the customer's technical team. Where customers report custom object usage, we create the equivalent custom object in Twenty via the Metadata API before importing data. Lookup relationships to standard objects (Person, Company) are resolved at migration time using the relationship data extracted during discovery.

Tags export as flat key-value pairs per contact. We map them directly to Twenty's tag field on the Person record. We flag any tags that exceed Twenty's character limits before import and map them as comma-separated values within the field maximum. If the customer uses tags for content classification as well as contact segmentation, we note the dual usage during scoping and recommend separate fields for each use case.

File attachments associated with contacts or campaigns are not available via the platform's documented export path. We flag attachments as out of scope and recommend that customers export attachments separately via the platform's UI export feature before the cutover date. Attachments can be re-linked post-migration by re-uploading to Twenty and associating them with the corresponding Person or Company record manually or via the Twenty API.

Marketing Tools Growth Marketing Platform Owner records map to Twenty User accounts. We resolve owners by email match. Any source Owner without a matching Twenty User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner resolution must complete before any record with an OwnerId reference is imported.