Migrate from Ascora to Twenty CRM

Ascora Customers map directly to Twenty People. Each Customer record carries name, email, phone, and address fields that translate to Twenty People fields without transformation. The Customer's internal ID is stored as Source_System_ID__c for delta-run de-duplication. This cross-reference enables the migration pipeline to detect and skip duplicate records during subsequent import runs, maintaining data integrity across the migration timeline.

When an Ascora Customer record represents a business entity (rather than an individual), it maps to a Twenty Company. This requires flagging at audit time — Ascora does not enforce a Company/Individual split, so business-type customers are identified by domain name presence or explicit business-type flag if configured.

Ascora Sites are service-location records linked to Customers — address, site name, site contact, equipment list. Twenty has no native Site object. We create a custom Site__c object with fields for address, site contact name/phone, and a relation to the Company representing the Customer. Each Job in Ascora links to a Site; this relation migrates as a lookup field on the Opportunity.

Ascora Jobs map to Twenty Opportunities — the job name becomes the Opportunity name, job amount maps to Opportunity amount, and the job's close date maps to the Opportunity close date. The job status value (Quoted, In Progress, Completed, Invoiced) maps to a custom Stage__c pick-list field on the Opportunity, not Twenty's native stage, because Twenty's stage is pipeline-specific.

Ascora job status values are mapped one-by-one to custom pick-list values in Twenty. Quoted maps to a prospecting stage, In Progress maps to a mid-pipeline stage, Completed maps to a closed-won value, Invoiced maps to a post-close stage. The mapping is documented and applied during CSV import transformation.

Ascora Quotations are separate records linked to Jobs. The quoted value migrates as a custom currency field on the Opportunity. Quote status (Sent, Accepted, Declined) becomes a separate custom pick-list field. Full quotation line items require a custom Quote_Line_Items__c custom object with a relation to Opportunity if line-item detail must be preserved.

Ascora invoices have no direct equivalent in Twenty CRM — Twenty has no native invoicing module. Invoice number, amount, and status migrate as custom fields on the Opportunity for historical reference. Ongoing invoicing must continue in the accounting integration (Xero, QuickBooks, or MYOB) outside Twenty.

Ascora custom forms capture field data (site sign-off name, equipment model, job notes) via field codes embedded in Word templates. Each field code becomes a Twenty custom field on the Opportunity object. Fields must be pre-created in Twenty Settings → Data Model before the CSV import runs — CSV import creates records, not fields.

Ascora job notes and activity log entries migrate as Twenty Notes attached to the corresponding Opportunity record. Original timestamps and author names are preserved. Activity type (call, site visit, etc.) is stored as a custom type field on the Note for filtering in Twenty's view.

Ascora file attachments on jobs (photos, signed forms, equipment receipts) cannot be carried via CSV import into Twenty. We export files from Ascora and re-upload them to Twenty manually or via API after go-live. File-to-record linking is rebuilt using Twenty's attachment model.

Ascora jobs are assigned to technicians or staff members. Twenty requires all Workspace Members to accept an invitation before user references can map. We resolve Ascora owner emails against Twenty Workspace Members — unmatched owners are flagged before migration and assigned to a fallback user.

Ascora integration links to Xero, QuickBooks, or MYOB are configuration-level connections that do not carry over. We document which accounting tool was connected per Customer and per Invoice so the team can reconnect the accounting integration in Twenty after go-live.