Migrate from Orderry to Twenty CRM

Orderry clients map directly to Twenty People records. We preserve the client name, email, phone, job title, and address fields as standard Twenty People fields. Owner assignment in Orderry resolves to a Twenty workspace member by email match before the migration runs.

Orderry company records map 1:1 to Twenty Companies. We preserve company name, domain, industry, employee count, and address. Parent-company relationships in Orderry migrate as a custom Parent_Company__c field on the child Company record in Twenty since Twenty has no native parent-account hierarchy.

Orderry work orders have no native Twenty equivalent. We map the work order name to Opportunity.Name, amount to Opportunity.Amount, and close date to Opportunity.CloseDate. The work-order type, priority, and status migrate as custom pick-list fields on a WorkOrder__c custom object linked to the Opportunity.

Orderry work-order line items (product, quantity, unit price, discount) do not fit Twenty's standard schema. We create a WorkOrderItem__c custom object with relation fields back to the parent WorkOrder__c record, then import line items after the parent Opportunity is created to satisfy Twenty's foreign-key integrity rules.

Orderry assets (serialized equipment tracked per client) have no Twenty equivalent. We create an Asset__c custom object with fields for asset name, serial number, type, and a relation to the client People record. This preserves the equipment history linked to each client account.

Orderry estimates map to Twenty Opportunities. The estimate total becomes Opportunity.Amount, and the estimate status (Draft, Sent, Accepted, Declined) maps to a custom Estimate_Status__c pick-list field on the Opportunity. If the estimate converted to a work order, we link the resulting Opportunity to the original estimate reference stored in a custom field.

Orderry inventory items (product name, SKU, stock level, cost, warehouse) have no Twenty equivalent. We create an InventoryItem__c custom object with fields for all key inventory attributes. If inventory is used purely operationally (not for sales pipeline tracking), we document it as a candidate for a separate inventory system rather than the CRM.

Orderry employee records map to Twenty Workspace Members. Email is the join key. Active Orderry employees who will use Twenty must receive their workspace invitation and accept it before the migration runs, otherwise owner assignments on records will fail to resolve and fall back to a designated fallback user.

Orderry ticket notes and activity notes attach to clients and work orders. We map these to Twenty Notes linked to the corresponding People or Opportunity record. Original creation timestamps are preserved as a custom Original_Created_At__c datetime field since Twenty's createdAt is set at import time.

Orderry allows user-defined fields on clients beyond the standard set. Every custom client field requires a matching custom field pre-created in Twenty's Settings → Data Model before the migration runs. We generate a field-creation checklist from the audit so your Twenty admin can pre-provision them.

Orderry records carry an owner_id pointing to an Orderry user. We resolve this to a Twenty Workspace Member by email. If the email has no match in Twenty, the record is assigned to a pre-agreed fallback user and flagged in the migration report for manual review.

Twenty sets CreatedAt and UpdatedAt at import time, overwriting the original Orderry timestamps. We preserve the original created_at as a custom Original_Create_Date__c datetime field and original updated_at as Original_Update_Date__c for reporting continuity on historical records. These preserved timestamps enable historical trend analysis and ensure that date‑based reports in Twenty reflect the true record creation timeline from Orderry.