Migrate from ConvergeHub to Twenty CRM

ConvergeHub Leads map to Twenty CRM Person records with personType set to Lead. The Lead's status, source, assignment, and any custom fields migrate as typed fields in Twenty. Email, phone, address, and company name fields map directly. If the Lead has an associated Account in ConvergeHub, we preserve the company reference as a link to a Twenty Company record created from the same Account.

ConvergeHub Contacts map to Twenty CRM Person records with personType set to Contact. Standard fields (name, email, phone, role, lifecycle stage) map to Twenty's name, email, phoneNumber, and jobTitle fields. The Contact-to-Account linkage migrates as a Company lookup. If ConvergeHub lifecycle stage values exist, they migrate to a custom field on the Person record for reporting continuity.

ConvergeHub Accounts map directly to Twenty CRM Company records. Industry, size, address, and custom properties migrate as typed fields. Account IDs are preserved in a reference field during staging so that all downstream Contact and Opportunity links resolve correctly. The Company record is created before any Person or Opportunity import to satisfy the required lookup dependency.

ConvergeHub Deals map to Twenty CRM Opportunity records. Stage, value, probability, expected close date, and owner assignment migrate directly. Pipeline stage mapping requires a configuration step in Twenty's workspace settings to match ConvergeHub's stage names to Twenty's Opportunity status options. Deal owner resolves to a Twenty User by email match.

Each ConvergeHub pipeline becomes a distinct set of Opportunity status values in Twenty. We extract all pipeline names and stage values from ConvergeHub's pipeline configuration, then configure Twenty's Opportunity object with matching status options before migration. Stage probability percentages are stored as a custom field if the customer requires them for forecasting.

ConvergeHub Cases map to Twenty CRM Tasks with the case's subject, status, priority, and description fields migrated. If the customer requires a dedicated support object (separate from sales Tasks), we pre-create a Case custom object in Twenty during schema design, map the case fields accordingly, and link each Case to the originating Person and Company via lookups. The choice is made during scoping based on the customer's support workflow maturity.

ConvergeHub Invoice records, including line items, totals, tax, and payment status, migrate to a custom Invoice object we create in Twenty's workspace. Invoice-to-Deal links are preserved as Opportunity lookups. Partially paid invoices and payment gateway transaction history do not migrate; we flag these for the customer's admin to reconcile against the source accounting system post-migration.

ConvergeHub Products (name, SKU, unit price, description) migrate to a Twenty custom Product object. Product associations to Deals are preserved via linked Opportunity records. If Twenty's native product catalog is available at the time of migration, we map to the native object instead of a custom object.

ConvergeHub Quotations carry product line items, pricing, and terms linked to Deals. We migrate quotation records and their line items to a custom Quotation object in Twenty, preserving the Opportunity lookup. If the customer adopts Twenty's native opportunity features for quotation management, we map to Opportunity instead during the scoping phase.

ConvergeHub Activities linked to Contacts, Leads, Deals, or Accounts migrate as Twenty Tasks with the activity type stored as a custom field. Call disposition, duration, and notes migrate to custom Task fields. Meeting activities migrate as Twenty Events with start time, end time, and location preserved. Each activity's associated Person or Opportunity link is resolved using the foreign key mapping constructed during the staging phase.

ConvergeHub documents and file attachments are downloaded from the platform UI, re-uploaded to Twenty's workspace file storage, and linked via URL reference to the parent record (Person, Company, or Opportunity). File metadata (name, type, size, upload date) migrates as a structured attachment record. Large binary attachments are handled in batches to avoid timeout during the upload phase.

ConvergeHub User records (name, email, role, ACL assignment) migrate to Twenty Users. Role names are mapped to Twenty's permission model during schema design. Owner assignments on Deals, Cases, and Activities resolve by matching ConvergeHub owner email to the Twenty User email after User records are present in the destination.