Migrate from Formitize to Twenty CRM

Formitize Client maps directly to Twenty Company. Formitize Client name maps to Twenty Company.name, and the Client domain maps to Company.website. The Client's full address fields map to the Twenty Company address composite. Custom fields on the Client record map to Twenty Company custom fields.

Formitize Contact maps to Twenty Person. Each Formitize Contact belongs to one Client via clientId, which maps to the Twenty Person.companyId relation. Formitize stores contact type or role as a custom field — we preserve it as a custom field on the Twenty Person record for reference. Formitize contacts without a Client are flagged for manual assignment to a Twenty Company.

Formitize Job maps to Twenty Opportunity. The Job name becomes Opportunity.name, the Job description becomes Opportunity.body, and Job status maps to a custom Opportunity.stage select field. The Job's linked Client becomes the Opportunity.companyId link. Job custom fields are mapped to Twenty Opportunity custom fields.

Formitize Job Status values (e.g., Scheduled, In Progress, Completed, Cancelled) have no native equivalent in Twenty's Opportunity object. We create a custom select field (Job_Status__c) on Twenty Opportunities and map the Formitize status values one-to-one into the custom field options. This preserves your operational workflow state within Twenty's CRM without requiring manual re-entry.

Formitize Assets belong to Asset Types and carry custom column data per type. Since Twenty has no native Asset object, we create a custom object named Asset and map asset name, description, asset type, and client link (via companyId relation) into the custom object. Custom columns from Formitize become custom fields on the Twenty Asset object.

Formitize stores asset latitude/longitude and zone data for physical locations. We create custom fields Latitude__c, Longitude__c, and Location_Zone__c on the Twenty Asset custom object to preserve this geographic context. If Formitize Location Zones are used, those are stored as a text custom field.

Formitize owner references on Jobs and Contacts are resolved by matching the owner's email address against Twenty Workspace Members. If a Formitize user has no matching email in Twenty, we flag the record and assign it to a fallback Workspace Member designated by your admin before migration.

Formitize custom fields on Clients, Contacts, and Jobs are defined in Settings and exposed via the API. Each custom field type (text, number, date, select) maps to the equivalent Twenty field type. We create the custom fields in Twenty under Settings → Data Model before the import runs so the CSV columns resolve correctly.

Formitize document attachments linked to Jobs are preserved as Attachments on the corresponding Twenty Opportunity record. We re-upload files to Twenty's attachment storage. If a Document has no linked Job, we attach it to the related Company or Person record based on the document's context in Formitize.

Formitize Smart Assist automations and Workflows (Auto Follow Up, Auto Task Actions, Auto Invoice) are not migratable to Twenty. Twenty uses a different event-action workflow model with limited sequencing. We export the Formitize workflow definitions as a JSON reference document so your Twenty admin can rebuild the logic in Twenty's workflow builder.