Migrate from Delta Sales CRM to Twenty CRM

Delta Contacts map directly to Twenty Persons. The contact's name, phone, email, address, and company linkage export from Delta as standard CSV fields and import into Twenty's Person object. Phone number format (especially leading zeros in international numbers) requires pre-import validation because CSV export can silently drop leading zeros. We compare a sample of phone number strings against Delta's source values before running the full import.

Delta Companies (Accounts) map to Twenty's Company object. The company name, website, address, and industry fields migrate 1:1. Company records must import before any Person records that reference them, because the Person.companyId lookup requires a valid Company ID to resolve. We extract the Company ID mapping table first and use it to resolve Person-Company links during Person import.

Delta Leads with a status of unqualified or early stage map to Twenty Person records (as Leads in Twenty's terminology if that object exists in the deployed version). Delta Leads that have progressed toward a deal map to Twenty Opportunity records with the person linked. We use Delta's lead status and assigned owner fields to determine the split at migration time and preserve the original lead source in a custom field for reporting continuity.

Delta Deals map to Twenty Opportunities. Deal name, amount, pipeline stage, probability, owner, expected close date, and associated contact and company links migrate to Twenty. The Delta pipeline stages (for example, Prospecting, Proposal, Negotiation, Won, Lost) map to Twenty's Opportunity stage values, which we configure before migration. We resolve the opportunity personId and companyId lookups using the ID mapping tables generated during Company and Person import.

Delta's customizable pipelines (multiple pipelines with custom stage definitions) map to a customized Opportunity stage configuration in Twenty. We extract each Delta pipeline's name, stage order, and stage probability values as metadata and configure Twenty's Opportunity stages accordingly before Deal migration begins. Stage probability percentages round to integer values supported by Twenty's stage model.

Delta Activities — including tasks, calls, meetings, reminders, and follow-ups — map to Twenty Task records. We export activity type, date, assignee, status, and notes. Delta's call duration and disposition fields migrate as custom task fields in Twenty. Date formats require normalization from Delta's export format to Twenty's expected ISO 8601 format before import. Activity records are linked to the parent Person or Company using the ID mapping tables built during Person and Company import.

Delta Products (name, price, unit, description, SKU if populated) map to Twenty Product records if the deployed Twenty instance includes a product management module. If Twenty's standard deployment does not include Products, we migrate product data as custom fields on the Opportunity object, mapping product name and price to custom Opportunity fields that the customer's Twenty admin configures before import.

Delta invoicing (invoice headers, line items, payment status linked to contacts, deals, and products) has no direct standard object equivalent in Twenty CRM's base deployment. We migrate invoice data as a custom object in Twenty, pre-configuring the schema with invoice number, amount, date, status, and linked Opportunity reference. The customer confirms whether invoicing will live inside Twenty or a separate billing system post-migration. If a separate system is planned, we migrate invoice records as an archived reference object without active linkage.

Delta Payment records (amount, date, method, linked invoice reference) migrate as a custom object linked to the corresponding Opportunity or Invoice custom object. Payment reconciliation between paid invoices and payment records requires matching the payment's associated invoice ID to the migrated invoice number, which we resolve using a lookup table built during invoice migration. If no invoice custom object is configured, payments migrate as Opportunity custom fields with payment date and amount.

Delta custom fields are supported across all major objects (Contacts, Companies, Leads, Deals, Activities). We export field definitions (name, data type, required/optional) and all populated values. Twenty's custom field mechanism must be configured in the Twenty instance before any import, because Twenty requires field schema to exist before record data can reference it. We pre-build the custom field schema during the scoping phase and deploy it before the first data import.

Delta Beat Plans assign route sequences to field reps visiting customers in a defined order — a concept with no standard equivalent in Twenty's base object model. We export beat plan name, assigned rep, route sequence, customer visit order, and scheduled visit dates. We deliver a written custom object specification for Twenty's admin to implement as a Route Plan custom object with fields for plan name, rep assignment, route step order, linked Company, and visit date. We do not import beat plan data as active records because the custom object must first be created in the Twenty schema by the admin.

Delta document uploads per record (up to 30-100 GB depending on plan) export as binary files with their associated record ID. We export files and their metadata (filename, record association, upload date) and note the file attachment volume before migration. Large attachment batches require chunked export and import. Whether Twenty's self-hosted deployment supports file attachments on Person or Company records depends on the specific version and hosting configuration — we confirm attachment support during scoping and flag any hosting storage constraints.