Migrate from Customer Database App to Twenty CRM

Customer Database App Contacts map to Twenty CRM Person records. Every user-defined custom field in the export column header becomes a Twenty custom field on the Person object. We infer the full field list from the first CSV export file and create the corresponding custom field definitions in Twenty before import. Name, phone, email, address, and standard properties map directly; custom properties map as typed fields (text, number, date, checkbox) based on value inspection.

Customer Database App does not have a native Company object; company data lives as custom fields on Contact records (e.g., company name field, industry field). We extract these into a normalized Company object in Twenty CRM, deduplicating by company name, then link each Person record back to the resolved Company via the Person's companyId field. This requires a two-pass import: Companies first, then People with resolved CompanyId.

Every Customer Database App contact supports unlimited user-defined fields with no enforced schema. We reverse-engineer the active field list from exported CSV column headers, classify each field by inferred type (text string, numeric value, ISO date, boolean flag), and create matching custom fields in Twenty CRM under the appropriate object before data load. If a field was added after the last export, we flag the discrepancy and require a fresh export.

Customer Database App's Kanban pipeline stages export as a label-value pair on each contact record. We extract the distinct stage names, preserve their sort order, and create corresponding Opportunity stage values in Twenty CRM. Stage probability percentages default to Twenty's standard values but can be customized if the customer provides the original percentages from Customer Database App.

Customer Database App does not have a standalone Opportunity object; pipeline state is embedded in contact records. We create Opportunity records in Twenty CRM for each contact that has a non-empty pipeline stage, linking to the Person and the resolved Company. The Opportunity close date is set from any date field in Customer Database App that corresponds to an expected close date, or set to 90 days forward if no close date exists.

Customer Database App exports groups and tags as comma-separated label strings on each contact record. We split these into individual Tag records in Twenty CRM, creating the tag if it does not already exist, and link it to the corresponding Person via the Tag's targetId and targetObjectName fields. Tags used for segmentation (e.g., VIP, churned, referral) are preserved as-is.

Birthday exports from Customer Database App as a date field on the contact record. We map it to a custom date field named birthday on the Person object in Twenty CRM. If Twenty's standard Person schema includes a birthday field in a later release, we map directly; otherwise it remains a custom date field.

Contact images and PDF exports of individual records can be bundled into a ZIP archive alongside the CSV. We attach each contact's image or PDF to the corresponding Person record in Twenty CRM using Twenty's attachment handling. Large ZIP archives are chunked to avoid upload timeouts, and each attachment is linked to the correct Person by email or name dedupe key.

Vouchers are a standalone object in Customer Database App with no direct equivalent in Twenty CRM's data model. Voucher balances are not exported via CSV at all. We do not migrate voucher data. We recommend exporting vouchers as a separate supplemental CSV for manual re-entry in Twenty or a dedicated voucher management tool post-migration.

Caller-ID logs and call history are transient device-level records stored on the mobile hardware, not persisted in the app database or exportable via CSV/VCF. These do not migrate. We recommend documenting current call-handling procedures separately for the customer's admin to re-establish in Twenty CRM or a linked telephony tool.