Migrate from Workbooks to Twenty CRM

Workbooks Organisation maps directly to Twenty Company. The Organisation name, address fields, industry classification, and any Workbooks custom fields transfer as typed Company fields or custom fields in Twenty. iFrame fields export as URL strings; the rendered content does not migrate. Company is inserted before Person records because the Person-to-Company lookup must be satisfied at the moment of Person insert.

Workbooks Person maps to Twenty Person with the Organisation-to-Company lookup preserved. Workbooks captures phone, email, job title, and department on the Person record; these transfer to Twenty Person fields. Workbooks custom fields on Person migrate to custom Person fields in Twenty. Note that Twenty's standard Person object ships with fewer default fields than Workbooks; we create missing standard fields in Settings → Data Model before importing Person data.

Workbooks Opportunities map to Twenty Opportunities with pipeline stage names, probability percentages, and expected close dates preserved. Stage probability weights transfer as Twenty stage probabilities. Opportunity owner assignment resolves via email match to the Twenty User record. Closed-Lost and Closed-Won dates migrate as standard Opportunity date fields.

Workbooks Cases map to Twenty Cases with status, priority, assigned user, related Organisation, description, and all case activity history preserved. The Organisation lookup resolves to the Company record inserted in the first migration phase. Open and resolved cases migrate with their full status history retained.

Workbooks Quotations contain a header (related Organisation, owner, validity date) and line items (product, quantity, price, discount). Twenty does not ship a native quotation object. We discuss two strategies during scoping: attach quotation PDFs as files to the related Opportunity, or create a Quotation custom object with line-item fields. The strategy choice depends on whether the customer needs quotation records to be queryable in Twenty reports.

Workbooks Invoices are only available on the Business tier. Invoice header data, line items, payment status, and credit note associations migrate as file attachments or to a custom Invoice object in Twenty. Invoice PDFs stored as Workbooks attachments are downloaded and reattached to the destination record. The Order-to-Invoice linkage present in Workbooks does not have a native Twenty equivalent; we document the linkage as a note field or custom field for manual reconciliation.

Workbooks Orders tie to an Organisation and quotation. Order headers, line items, and status migrate as file attachments or to a custom Order object in Twenty. The customer chooses the destination strategy during scoping. Order-to-Invoice linkage is preserved as a reference field; if the destination does not support the relationship natively, we add a custom text field for the related invoice reference.

Workbooks Activities represent logged calls, emails, meetings, and tasks linked to an Organisation or Person. We map activity type, date, duration, subject, description, and owner to Twenty Note or Task records. Activity history is bulk-extracted in batches of 5,000 to avoid Workbooks save latency during large dataset exports. The original timestamp is preserved on the migrated record.

Workbooks Campaigns track marketing initiatives and their associated leads. Campaign name, status, start and end dates, and associated lead and person memberships migrate to Twenty Campaign. Campaign response data migrates as Campaign Member records. If the customer used Workbooks campaign scoring, we preserve the score in a custom Campaign field.

Workbooks Leads hold pre-conversion prospect data with source, status, rating, and assigned owner. Leads map directly to Twenty Lead. The original Workbooks Lead status is preserved in a custom field for audit and reporting continuity.

Workbooks custom fields of types text, number, date, dropdown, checkbox, and file upload migrate to Twenty custom fields of equivalent type. All custom fields must be created in Twenty Settings → Data Model before any data import begins; Twenty's CSV import creates records, not fields. File-upload fields require a separate binary extraction and reattachment step.

Workbooks deployments with bespoke record types map to Twenty custom objects created via the /metadata API. We pre-create the destination schema including all fields, field types, and lookup relationships before importing custom object records. Lookup references to standard objects (Company, Person, Opportunity, Case) are resolved in dependency order.