Migrate from Freshmarketer to Twenty CRM

Freshmarketer Contact records map to Twenty Person records. Email address is the dedupe key. Standard fields (name, email, phone, address, lifecycle stage) map directly. Custom contact fields require field-level mapping against Twenty's Data Model API; field types (dropdown, multi-select, date) are resolved during the transform phase. Owner assignment from Freshmarketer maps to a Twenty team member via email match lookup.

Freshmarketer Company records map to Twenty Company records. Company name, domain, industry, and address migrate directly. Company-contact associations are preserved at migration time by resolving the org_contact_id link to the corresponding Twenty Person record. If the company domain maps to an existing Twenty Company, records are merged on domain match rather than created fresh.

Freshmarketer Deal records map to Twenty Opportunity records. Deal stage, amount, close date, owner, and associated company/person link migrate directly. Pipeline stage names from Freshmarketer are mapped to Twenty Opportunity stage values during configuration. Custom deal fields require mapping against Twenty's Opportunity custom field schema before import.

Freshmarketer pipelines map to Twenty Pipeline records with corresponding Stage records. We configure pipeline and stage names in Twenty's Data Model before migration begins. Probability percentages from Freshmarketer pipeline stages migrate to Twenty stage weights.

Freshmarketer activity logs (email conversations, sales activities, calls) migrate as Task records in Twenty. Each activity retains its original timestamp for timeline ordering. We flag attachments linked to activity records for separate file export and linked-record creation in Twenty. The activity type (call, email, meeting, note) is stored in a custom Task type field.

Freshmarketer Segments use filter criteria for audience selection and have no direct equivalent in Twenty CRM. We map segment criteria to Twenty's filter-and-sort capabilities on the Person and Company objects. If the customer needs static audience lists, we create a custom field on Person (segment_name) and populate it with the segment names the contact belonged to at migration time.

Freshmarketer Journeys (marketing automation workflows) cannot be exported as executable logic via API. We capture Journey configuration as a structured JSON document listing each step, trigger condition, delay, and action. We also capture the set of contacts enrolled in each Journey at cutover and deliver a replay plan document so the customer's admin can rebuild equivalent sequences in their chosen marketing automation tool. Journeys do not execute in Twenty CRM.

Custom fields on Freshmarketer contacts, companies, and deals are supported via API but require explicit per-field mapping. We pre-create matching custom fields in Twenty's Data Model (Settings > Data Model > object > Add Field) before data import begins. Field type differences such as Freshmarketer dropdown versus Twenty multi-select, date format differences (ISO 8601 vs MM/DD/YYYY), and multi-value field handling are resolved in the transform layer.

Freshmarketer User accounts (name, email, role, team) map to Twenty WorkspaceMember records. Owner references on Contacts, Companies, and Deals are remapped by email match to the corresponding WorkspaceMember. Users without a matching WorkspaceMember at migration time are placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Freshmarketer tags applied to contacts, companies, and deals migrate as a comma-separated string stored in a custom tag field on the corresponding Twenty object. No tag hierarchy exists in Freshmarketer, and Twenty does not have a native hierarchical tag model, so a flat migration preserves the full tag set.