Migrate from FreeCRM to Twenty CRM

FreeCRM Contact records with standard fields (name, email, phone, address) map directly to Twenty People. Template-driven custom fields are inventoried during discovery and pre-created as Twenty custom fields before import. Tags stored as comma-separated values on Contact are split into a Twenty multi-select field or Topics array. The related Company link migrates as a Company lookup on the People record. Owner email from FreeCRM resolves to a provisioned Twenty user.

FreeCRM Company records map to Twenty Company with name, domain, and industry fields preserved. The company domain becomes the Company URL field in Twenty. Parent-child relationship to Contacts migrates as the primary contact lookup on the Company record. Custom template fields on Company records are pre-created as Twenty custom fields and populated during the Company import phase before Contact import begins.

FreeCRM Lead records use the template system so field names vary per account. We extract the full field set during discovery and map lead-status and source fields into Twenty standard People fields. If the FreeCRM Lead represents a sales-qualified opportunity with an amount, it maps to a Twenty Opportunity linked to the People record. Progression between lead status values is preserved as a text field in Twenty for audit.

FreeCRM Deal records map to Twenty Opportunity. The deal amount, expected close date, and stage (stored as free text in FreeCRM) migrate with stage values mapped to Twenty pipeline columns during import. Free text stage names require a mapping table built during discovery. Owner email on the Deal resolves to a provisioned Twenty user. Pipeline stage order is preserved in Twenty's Opportunities view.

FreeCRM stages are account-defined text values stored per Deal rather than a structured stage object. We extract the complete stage list from all Deal records during discovery, map each to a Twenty Opportunity stage column, and configure the pipeline in Twenty before importing any Deal data. Stage ordering is preserved by setting the sort sequence on each Twenty stage column.

FreeCRM activity records (tasks, events, call logs) export as activity rows with a related-to link to a Contact or Company and a timestamp. We preserve the related-to link as a Twenty People or Company lookup and the timestamp as the Task due date or Note creation date. Call log disposition and duration migrate as custom fields on the Task record. Historical activity ordering may be partial because FreeCRM does not guarantee complete chronological export sequencing.

FreeCRM tags export as comma-separated values on Contact and Company records. We split each comma-separated string into individual values and map them to a Twenty multi-select field or to Twenty Topics with TopicAssignment records linked to the People or Company. The customer chooses tag strategy during scoping. Tags that function as labels map to Topics; tags that function as classification flags map to multi-select fields.

FreeCRM custom fields defined per-record via templates are inventoried across all active templates during discovery. Each unique field is typed (text, number, date, picklist, checkbox) and mapped to a Twenty custom field created in Settings → Data Model before any import. Fields that appear only on a specific template are created as Twenty custom fields but populated only for records using that template. Fields absent from a record's template are left blank in Twenty.

FreeCRM Pro supports invoice creation and export. Invoice records with line items, totals, and status migrate to a Twenty custom object (Invoice) if the customer requests full invoice history, or as Note records with structured content if the volume does not justify a custom object. Invoice-to-Contact or invoice-to-Company relationships migrate as lookup links in Twenty.

FreeCRM user accounts and owner email assignments on records require reconciliation against Twenty's user list. We extract every distinct owner email from FreeCRM records, match by email to provisioned Twenty users, and hold any unresolvable assignments in a reconciliation queue. The customer's admin provisions missing Twenty users before record import resumes. Owner assignments on records are applied after user provisioning is confirmed.