Migrate from Combit CRM to Twenty CRM

Discovery and extraction method selection

We audit the Combit CRM deployment (on-premise or cloud), confirm database access availability for on-premise instances, and identify a bilingual contact or engage a German-speaking analyst for the discovery phase. We catalog all standard and custom field definitions, pipeline stages, address-contact relationships, activity types, and any existing workflow definitions. The discovery output is a written migration scope that specifies extraction method (database query or CSV export), record counts per object, and any German-to-English field label translations required. We also confirm the target Twenty deployment method (cloud-hosted or self-hosted) and provision the Twenty workspace.

Schema design and Twenty workspace preparation

We design the destination schema in Twenty. This includes creating custom objects and custom fields to match the Combit data model, configuring Opportunity pipelines and statuses that mirror Combit deal stages, and setting up the Twenty workspace structure (Members, roles, data model). All custom fields and custom objects are created in Twenty before any data import begins, per Twenty's import requirements. We map Combit Address records to Twenty address fields or a linked Address/Location object based on the customer's address multiplicity requirements.

Data extraction and transformation

For on-premise deployments we run extraction queries against the Combit database, documenting the table structure, primary keys, and foreign key relationships. For cloud deployments we generate CSV exports from Combit's built-in export functionality, exporting each object type separately. We transform Combit field values to match Twenty's data types, translate German-language picklist values to their English equivalents using the discovery mapping, and resolve address-to-contact linkages using the Combit Address ID as a foreign key. We apply deduplication rules during transformation if the customer has identified duplicate Combit records to clean.

Sandbox or staging migration and reconciliation

We run a test migration into the Twenty workspace using production-like data volume. The customer's team spot-checks 25-50 records per object against the Combit source, verifying field mapping accuracy, relationship integrity (People-Company, Opportunity-Company), and activity timeline completeness. We reconcile row counts from the extraction output against records loaded in Twenty and resolve any mapping corrections before proceeding to production migration. This step catches German field label translation errors and custom field creation gaps before any data lands in the production workspace.

Owner reconciliation and Twenty member provisioning

We extract every distinct Combit User and Owner referenced on People, Company, Opportunity, and Activity records and match by email against the Twenty workspace Members. Users must exist in Twenty before any records with owner references are imported. The customer's admin provisions any missing Members and waits for acceptance. Owner assignment history is preserved as a custom field on migrated records if the customer requires an audit trail of original assignments.

Production migration in dependency order

We run production migration in record-dependency order: Address records (if separate entity), Companies, People (with Address and Company lookups resolved), Opportunities (with Company and Member lookups resolved), and Activity history (Tasks and Events). Each phase emits a row-count reconciliation report before the next phase begins. We use bulk import with chunking and backoff handling to manage volume. We flag any records with unresolved owner references for the customer's admin to address before resuming.

Cutover, validation, and workflow rebuild handoff

We freeze Combit CRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Twenty as the system of record. We deliver the Combit workflow and automation inventory document with each workflow's trigger, conditions, and actions mapped to a recommended Twenty workflow configuration. We support a one-week post-cutover window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild Combit workflows in Twenty as part of the migration scope; that work is handled by the customer's admin or a Twenty implementation partner.