Migrate from FowCRM to Twenty CRM

FowCRM Accounts map directly to Twenty Companies. The Account name, industry, website, address fields, and any custom properties attached to the Account model migrate as standard and custom Company fields. We enumerate FowCRM's Account Model first to capture all active custom fields before extracting data, then create matching custom fields in Twenty via the /metadata API before the Company import batch runs.

FowCRM Contacts map to Twenty Person records. Contacts are linked to Accounts via account_id, which we resolve to the migrated Company record at import time using the Company name or domain as the lookup key. Lifecycle stages and contact roles from FowCRM migrate as custom fields on the Person record. Email, phone, title, and address fields map directly to Twenty's standard Person fields.

FowCRM Deals map to Twenty Opportunities. The Deal's linked Account resolves to the migrated Company; the linked Contact resolves to the migrated Person. Deal amount, close date, and stage migrate to Opportunity amount, closeDate, and stage. We map FowCRM's pipeline stage names to Twenty's stage values during the schema design phase, before any Opportunity data is loaded.

FowCRM Pipelines with configurable stages map to Twenty as a combination of Opportunity stage values plus an optional pipeline-name custom field. If the customer uses multiple FowCRM Pipelines to represent different business lines, we create a pipeline_name custom field on Opportunity and populate it during Deal migration so that filtering by pipeline is preserved in Twenty.

FowCRM Cases (Requests and Complaints) are tier-gated on Professional and Enterprise plans. If the customer holds a qualifying tier and Cases exist in the API, we migrate them as a Twenty custom object named Case with status, priority, case_type custom fields, and a link to the related Company. Standard FowCRM instances on the Standard tier do not expose Case data in the API — we confirm tier during discovery and skip Case export gracefully if the endpoints return 403 or empty arrays.

FowCRM Custom Fields require a two-step discovery process: enumerate Models via /Models, then fetch Field definitions for each Model via /Fields. Many migration tools query the Fields endpoint directly and return empty results. We run the Model enumeration step first, build a complete model-to-field index, then export custom field data for each Model. In Twenty, custom fields are created via the /metadata API with the correct field type (text, number, date, select) matched from FowCRM's field definition before the corresponding record data loads.

FowCRM Activity records linked to Contacts or Accounts migrate to Twenty Activities attached to the corresponding Person or Company. Activity type (call, email, meeting, note) maps to Twenty's activity type enum. Timestamp and body content migrate directly. We preserve the activity-to-record association carefully to avoid orphaned activities — the Contact or Account reference is resolved to the migrated Person or Company ID before the Activity insert batch runs.

FowCRM Survey definitions and response data are exported as structured JSON because Twenty has no native survey object. Survey questions and response schemas differ significantly between platforms, so we treat survey data as a mapping exercise with the full JSON preserved as a custom field on a Survey custom object. If survey responses number in the thousands, we store them as a JSON array field rather than creating individual custom object records.

FowCRM Users (email, role, department) export by email. In Twenty, the equivalent is a WorkspaceMember. We resolve owners by email match against the Twenty workspace. Any FowCRM User without a matching WorkspaceMember in Twenty goes to a reconciliation queue for the customer to provision before record import resumes. User-to-Deal and User-to-Contact assignments migrate as Opportunity and Person owner references once the WorkspaceMember mapping is validated.

FowCRM integrations and webhook subscriptions are not exposed via the public API. The integration configurations that manage connections to connected apps, third-party tools, and inbound webhook receivers cannot be exported programmatically. We do not migrate integrations — we deliver a written inventory of every active FowCRM integration (identified from the customer's configuration documentation or UI screenshots provided during discovery) with the recommended setup steps for Twenty's equivalent mechanism.