Migrate from Centrium CRM to Twenty CRM

Centrium Contacts marked as individual people map directly to Twenty Person records. Standard fields (name, email, phone, address) transfer as typed fields. We use email as the dedupe key during import to prevent duplicate Person records from multiple exports. Any orphaned email addresses with no valid domain are flagged in the reconciliation report for manual review.

Centrium does not have a separate Companies/Accounts object — organizations are stored as Contact records with an organization flag. We identify all flagged records during preprocessing, extract them as a distinct set, and create Company records in Twenty. The individual Person records that reference these organizations are then linked via a foreign key to the newly created Company record. This preprocessing step adds one to two days to the migration timeline for accounts with large organization lists and is the most common source of mapping errors if skipped.

Centrium Deals map to Twenty Opportunities. The Centrium status field (won/open/lost) maps to the closest Twenty Opportunity stage value. Stage names from Centrium custom stage configurations transfer as custom Opportunity stage labels. The deal amount and close date transfer to amount and closeDate. We note in the validation report that Centrium's flat status model cannot reconstruct multi-stage progression history in Twenty.

Centrium's deal stages (lead, offer sent, negotiations, won, lost) are configurable per account but stored as a flat list without probabilities or historical timestamps. We map each Centrium stage to a Twenty Opportunity stage, assign probability percentages closest to the customer's historical close rates, and configure the pipeline layout in Twenty Settings before migration. If the customer uses custom stage names beyond won/open/lost, we create matching stage values via Twenty's pipeline configuration.

Centrium Tasks migrate to Twenty Tasks with due date, status, priority, and description preserved. Task assignments resolve against the User mapping by email — the assignee email in Centrium must match an invited Twenty workspace member. Open tasks and completed tasks both migrate; only deleted tasks are excluded. Tasks linked to Centrium Deals are re-linked to the corresponding Twenty Opportunity during import using the deal-ID mapping as the cross-reference.

Centrium Projects are lightweight containers linking tasks and contacts. Twenty does not have a native Project object, so we create a Project custom object via the Twenty metadata API during the schema design phase. The custom object includes fields for project name, linked tasks (stored as a text list of task references), and associated contacts. If the customer's project structure is more complex (milestones, dependencies, sub-tasks), we recommend a separate project management tool post-migration and flag this during scoping.

Centrium Notes migrate to Twenty Note records. The note body, author, and creation timestamp transfer. Notes attached to a specific Contact in Centrium are linked in Twenty to the corresponding Person record; notes attached to a Deal are linked to the Opportunity. Centrium notes are flat text only — multi-message conversation threads do not exist in Centrium and therefore have no equivalent to migrate.

Centrium custom fields on Contact, Deal, Task, and Project objects extract as name-value pairs during preprocessing. We read the field definition from the Centrium export metadata and create the corresponding custom fields in Twenty via the Settings → Data Model interface before import. Field types map to their nearest Twenty equivalents: text to text, number to number, date to date, picklist to select. Fields with no equivalent type default to text.

Files attached to Centrium Contacts, Deals, and Projects cannot be retrieved via a public API. We audit total attachment size during discovery, flag it in the migration scope document, and recommend either external archival (shared drive, S3 bucket) with a lookup reference migrated, or purchasing sufficient Twenty storage for direct attachment migration. Direct attachment migration requires the customer to manually download files from the Centrium UI and provide them in a structured folder format; we do not automate UI-based file retrieval.

Centrium user records include name, email, and team role. We match source users to Twenty workspace members by email. Users without a matching email in the Twenty workspace are held in an orphan queue. The customer must invite all expected users to the Twenty workspace before the migration runs because task assignee references and opportunity owner assignments require a valid Twenty User record to resolve.

Centrium custom field definitions are extracted as a schema manifest during preprocessing. Before any data import, we use Twenty's metadata API to provision the corresponding custom fields on the relevant objects (Person, Company, Opportunity, Task, Project). Fields must exist in Twenty before CSV import begins — importing into undefined fields results in silent data loss. This is a blocking dependency in the migration sequence.