Migrate from Method CRM to Twenty CRM

Method CRM Contacts map to Twenty People records. Standard fields (name, email, phone, address, company association) migrate directly. Custom fields on Contact map to custom fields on People, with field type mapping (text to text, number to number, date to date, select to select). Email uniqueness validation in Twenty requires deduping by email before insert.

Method Companies map to Twenty Companies with a 1:1 field mapping. Company name, domain, address, and industry custom fields migrate directly. The Company record must exist before importing any People records that reference it via a company association, so we sequence Companies first in all migration phases.

Method Opportunities map to Twenty Opportunities. The deal amount, close date, stage name, owner, and associated Company and Contact references all transfer. Stage names migrate as-is to Twenty's Opportunities select field; teams configure custom stage values in Twenty Settings → Data Model after migration if their pipeline differs from Twenty's defaults.

Method Activities with type CALL migrate to Twenty Task records with a call category field; type MEETING migrates to Task with meeting category; type NOTE migrates to Twenty Note records. We preserve activity date, description, and owner assignment. Note that Method's activity links to Contact or Company may require re-association in Twenty's activity timeline UI post-import because Twenty links activities through People and Company record references.

Method Estimates contain line items, totals, status, and QuickBooks entity references. Twenty has no estimate object, so we map estimate data to Opportunity records with the estimate value recorded as the opportunity amount and the original line-item detail preserved as a Note attachment on the Opportunity. The QB linkage metadata is flagged in a custom field for manual resolution since Twenty has no accounting sync layer.

Method Invoices store line items, tax codes, payment status, and QB entity references. We map invoice totals to a closed-won Opportunity in Twenty with the paid amount recorded in a custom currency field. Unpaid balance is flagged in a custom field. Because Twenty has no invoice or payment-tracking module, historical invoice status does not update automatically; the customer reviews these records post-migration.

Method Sales Orders (Pro and Enterprise tiers) map to Twenty Opportunities with a custom status field indicating sales order origin. Line items and order totals migrate to Opportunity amount with line-item detail preserved as an attached note. QB entity references are flagged in a custom field for admin review.

Method CRM custom fields on any standard object (Contact, Company, Opportunity) map to Twenty custom fields via the Settings → Data Model panel. We extract the full list of custom field names, data types, and picklist values during discovery and pre-create the equivalent fields in Twenty before any data import begins. Required field settings and unique constraints are evaluated against data quality before being enforced in Twenty.

Method CRM custom tables migrate to Twenty custom objects. We extract the full schema including field names, types, and relationship definitions during discovery. In Twenty, we create matching custom objects via Settings → Data Model, including all field types (text, number, select, relation, date). Many-to-many and many-to-one relationships are preserved as Twenty relation fields. This requires schema design before data migration begins.

Method CRM user records map to Twenty workspace Members. We extract all distinct owners referenced on Contact, Company, and Opportunity records and map them to Twenty Members by email. Active and inactive status is preserved. If a Method owner has no corresponding Twenty user, the record is assigned to a placeholder owner and flagged for manual resolution.

Method CRM tags on Contacts and Companies migrate as flat label strings. We import tags into a Twenty custom text field as comma-separated values or into a custom select field if the tag vocabulary is stable and enumerated. The customer chooses the target field type during scoping based on how they intend to use tags in Twenty.

Method CRM Files and attachments migrate as binary records with metadata (filename, MIME type, upload date, uploader). We download file content from Method's Files API and re-upload to Twenty, then link each file to its parent record (Contact, Company, or Opportunity) using Twenty's file attachment association. Files must be imported after their parent records to satisfy the linkage requirement.