Migrate from FunnelMaker to Twenty CRM

FunnelMaker Contacts map directly to Twenty CRM Person records. Every standard contact field (name, email, phone, address) and all user-defined fields migrate as typed fields on the Person object. We use FunnelMaker's contact ID as an external ID (displayName or a custom field) so that related records (Activities, Opportunities) can resolve the Person reference via lookup during import. FunnelMaker's contact tier cap does not affect migration into Twenty, which has no per-contact limit.

FunnelMaker Company records map to Twenty CRM Company. Company-contact associations are preserved using the FunnelMaker contact-to-company link, resolved as a Company lookup on the Person record during import. All company-level custom fields migrate as custom fields on Twenty's Company object after the schema is pre-created via Twenty's /metadata API.

FunnelMaker Opportunity records map to Twenty CRM Opportunity with a direct 1:1 field mapping. Pipeline stage names from FunnelMaker become Opportunity stage values in Twenty. Closed-Lost and Closed-Won reason fields migrate as custom text fields if they exist in FunnelMaker. We resolve Opportunity owner to a Twenty User by email match and set the AccountId (Company lookup) before Opportunity import.

FunnelMaker drag-and-drop pipeline stages map to Twenty CRM Opportunity stage values. Each FunnelMaker pipeline becomes a separate set of stage values in Twenty's Opportunity pipeline. Stage probability percentages migrate as decimal values on each stage. We configure the pipeline stages in Twenty's workspace settings before Opportunities are imported.

FunnelMaker Activity records (calls, emails, tasks, notes) map to Twenty CRM Task or Note depending on type. Call metadata (duration, timestamp, owner) migrates as Task records with a custom call-specific field set. Email activities migrate as Note records attached to the Person or Opportunity. Activity date ordering is preserved by setting the Task or Note createdAt timestamp to the original FunnelMaker activity timestamp. Full email content migrates as Note body text.

FunnelMaker drip campaigns are email sequences with time-based steps and contact-segment triggers. We map the campaign structure (step order, delay, email template reference, segment criteria) into a written document that describes each step and its recommended Twenty equivalent. The customer rebuilds drip campaigns in their chosen email marketing tool (e.g., Mailchimp, Klaviyo, or a custom sequence tool) after migration. Drip campaign logic does not transfer as automation code.

FunnelMaker Workflows are automation rules with trigger conditions, conditional branching, time delays, and action types that have no direct equivalent in Twenty CRM's workflow model. We document every active Workflow during discovery, listing the trigger, each condition branch, the resulting action, and the records affected. The customer reviews this document and rebuilds workflows using Twenty's available automation capabilities or a third-party tool.

FunnelMaker custom objects (unlimited on all tiers) migrate to Twenty CRM custom objects of matching API name. We pre-create the destination custom object schema via Twenty's /metadata API, including all custom fields with correct types (text, number, date, boolean, select, multi-select, relation), before importing any records. Lookup relationships between custom objects and standard objects (Person, Company, Opportunity) are resolved at import time using the external IDs we assigned during the FunnelMaker export phase.

FunnelMaker lead score values migrate as a custom numeric field on the Twenty CRM Person object (e.g., lead_score__c). The scoring rule logic is documented separately as a reference for the customer to rebuild in Twenty or a third-party scoring tool. Score history (historical score changes over time) does not migrate because FunnelMaker stores it as a calculated value rather than discrete records.

FunnelMaker tags and group memberships are mapped to either a multi-select custom field on Person (for organizational tags like 'enterprise', 'SMB') or a list/segment membership in Twenty's data model depending on how the customer uses them. We document the tag distribution during scoping so the customer decides whether tags become filterable fields or separate list records.

FunnelMaker document signature requests and stored files migrate as Note records with document metadata (filename, upload date, signing status) in the Note body. The actual file content (PDF, contract) does not migrate unless the customer provides a file URL or storage link. We preserve the relationship between the document and its parent Person or Opportunity using Twenty's Note linking.