Migrate from CRM.io by 500apps to Twenty CRM

CRM.io Contact records (name, email, phone, company association) map 1:1 to Twenty CRM Person records. We extract the CSV export, normalize the name field into firstName and lastName, and ingest via Twenty's GraphQL mutations. The CRM.io company association (Account link) is preserved as a WorkspaceMember link or CompanyPersonRelation record in Twenty after the Company records are loaded. Email addresses serve as the dedupe key for Person records.

CRM.io Lead records (name, source, status, owner) map to Twenty CRM Person records with a type discriminator field set to LEAD. If Twenty's destination workspace uses the legacy Person model without type separation, Leads and Contacts merge into the same Person table using email as the dedupe key, with a source_system field set to CRM.io_Lead or CRM.io_Contact for audit. Lead status values from CRM.io (New, Contacted, Qualified, etc.) map to a custom picklist field in Twenty.

CRM.io Account records (business name, industry, size, address) map 1:1 to Twenty CRM Company records. We extract the Accounts CSV, map the industry and employee_count fields to their Twenty equivalents, and ingest Companies before any Person or Opportunity load to satisfy the required CompanyId lookup. Company domain from the address data is preserved for future enrichment.

CRM.io Deal records (stage, value, close date, owner, linked Account) map to Twenty CRM Opportunity records. The critical migration step is reconstructing the Account-to-Deal relationship from CRM.io's flat CSV export, which does not include the foreign key reference. We build a compound key from Deal name and associated Account name, cross-reference against the Account CSV export, and resolve the CompanyId in Twenty at migration time before Opportunity ingestion.

CRM.io's configurable pipeline stages export as stage names in the Deals CSV but there is no API to retrieve the active pipeline configuration or stage ordering. We infer stage order from deal record distribution and the customer's input during scoping, then configure Twenty's pipeline stages to match. Stage probability percentages are requested from the customer or inferred from stage names (e.g., Closed Won = 100%, Negotiation = 75%) and set as custom fields in Twenty.

CRM.io Activities (calls, emails, tasks, meetings) link to Contacts or Deals in the UI, but the parent object ID may not be reliably present in the CSV export. We reconstruct Activity-to-Person and Activity-to-Opportunity associations using a combination of date matching, subject text matching, and the owner email resolution. Each activity type from CRM.io maps to a Twenty TimelineEvent with the corresponding type discriminator (CALL, EMAIL, TASK, NOTE) and the original timestamp preserved for timeline ordering.

CRM.io Document Management stores file attachments with metadata (filename, type, associated record ID) in the CSV export, but binary file content does not export via standard CSV. We export the metadata and build an Attachment record in Twenty with a link to the original CRM.io file reference. For the binary files, we provide a separate bulk transfer via secure shared storage (preferred for large datasets) or manual re-upload instructions for the customer's admin team post-migration. This step is scoped separately from the core migration.

CRM.io exports Tags as comma-separated values within the Contact or Deal CSV rows. We parse these into an array field in Twenty, either as a native multi-select tag field if configured, or as a normalized Tag table with TagRelation records linked to the Person or Opportunity. The customer chooses the tag strategy during scoping.

CRM.io assigns record ownership to Users. We extract Owner names and emails from every record and map them to Twenty User accounts via a customer-provided lookup table during scoping. Any CRM.io Owner without a matching Twenty User is held in a reconciliation queue; the customer provisions the User in Twenty before record ingestion resumes.

CRM.io Email Templates are UI-stored templates that do not export via standard CSV. We do not migrate Email Templates. Customers who need to preserve templates should manually export them from within the CRM.io UI before the wind-down date. We include a note in the scoping checklist to flag this for the customer's admin team.

CRM.io explicitly states 'Customization Possible: No'. There are no custom fields, custom objects, or extended schemas documented for the platform. The flat CRM.io schema is fully captured in the standard object exports above.