Migrate from ZeyOS to Twenty CRM

ZeyOS Accounts are the primary company-level records and map directly to Twenty CRM's Company object. We preserve the account ID, name, website, address fields, and any extdata custom fields. Twenty's Company object supports custom fields created via Settings → Data Model, and we map ZeyOS extdata key-value pairs into identically named Twenty custom fields using the same data types.

ZeyOS Contacts map to Twenty CRM's Person object with the name, email, phone, and address fields preserved. The parent Account relationship maps to a Company relation in Twenty's data model. Any extdata nickname or custom per-contact fields migrate as custom Person fields.

ZeyOS Leads are a distinct CRM object separate from Contacts. Twenty CRM does not have a separate Lead object; all person records live in the Person object. We import ZeyOS Leads as Person records and set a custom lead_status custom field to preserve the original ZeyOS lead stage (new, contacted, qualified, lost). The customer decides whether to merge these with existing Contact-sourced Person records during deduplication.

ZeyOS Items represent the inventory/product catalog with barcode, model, and custom fields. If Twenty is configured with a custom Product object via Settings → Data Model, we map Items 1:1 to that custom object. If no custom Product object exists, we map Items to Opportunity Line Items during Deal migration with the product name, SKU, and price preserved.

ZeyOS Projects contain Tasks, subtasks, and time entries and map partially to Twenty CRM. We import the Project as a Twenty Opportunity (using the project name and estimated value) and import child Tasks as Twenty Task records linked to the Opportunity via the OpportunitiesAccount task relations. Time entries map as Task custom fields or notes. ZeyOS's native project management depth (Gantt, resource allocation) does not have a direct Twenty equivalent and requires admin review post-migration.

ZeyOS Tasks belonging to Projects map to Twenty CRM Task records. We preserve the task title, description, assignee (resolved to Twenty User by email), due date, and status. Tasks without a parent Project map as standalone Tasks. ZeyOS's custom workflow flags on Tasks migrate as custom Task fields in Twenty.

ZeyOS Tickets with email integration and conversation history map to Twenty CRM as Task records (using the task title and subject) with email conversations preserved as notes or Task comments. If the customer has a significant ticket volume, we recommend configuring a custom Ticket object in Twenty via Settings → Data Model before migration and mapping Tickets 1:1 to that object.

ZeyOS's five financial objects (Quotes, Orders, Deliveries, Invoices) form a billing pipeline with audit-lock immutability on booked invoices. Twenty CRM does not have a first-class Quotes or Invoice object in the standard data model. We import financial metadata (amount, date, status, line items) as custom fields on the corresponding Opportunity record, and preserve the full financial chronology as a written audit log document for the customer's admin. Invoice PDFs are imported as file attachments on the Opportunity.

ZeyOS Users who own records map to Twenty CRM Workspace Users. We resolve by email match. Inactive ZeyOS Users are flagged for post-migration admin review before deactivation in Twenty. Owner assignment on Contacts, Accounts, and Opportunities migrates by resolving the ZeyOS user reference to the Twenty User ID.

ZeyOS Activities linked to Accounts or Contacts map to Twenty CRM Task records (for calls and tasks) and Event records (for meetings). Email body content migrates as a Task or Comment with the timestamp preserved. Note attachments migrate as file attachments on the related Company or Person record. Activity timestamps convert from ZeyOS int8 epoch to ISO 8601 datetime strings during the transform phase.

ZeyOS files stored in the binfile column require binary blob download via the REST API individually. We download each blob, validate its MIME type and size (flagging files over 25MB for customer review), and re-upload to Twenty's attachment storage linked to the corresponding Company, Person, Opportunity, or Task record. Files with a record FK attach to the migrated parent record; files with a comment FK attach as notes.

ZeyOS exposes custom field definitions via the fields table and the extdata JSON column in the REST API. We read every extdata key during discovery, infer the data type (string, number, date, boolean, picklist), and pre-create matching custom fields in Twenty's data model (Settings → Data Model) before the record migration phase. Custom fields are created per object (Company, Person, Task, Opportunity) and mapped individually during import.