Migrate from Cetec ERP to Twenty CRM

Cetec Customer records map directly to Twenty CRM Company records. The customer name, address, phone, website, and type fields migrate as typed fields in Twenty. We flag the internal customer record (the company itself) during pre-migration audit because Cetec locks editing on that record once an order is linked; any intended rename or merge must be resolved before migration scope closes. The internal customer ID is held in a reconciliation queue until the customer's admin confirms the correct treatment (keep as-is, or re-link to the migrated Company record).

Cetec Lead records (distinct from Customers in the sales funnel) map to Twenty CRM Person records. The lead status, source, and owner fields map to the corresponding Twenty fields. A lead that has a linked Customer record from which it originated is linked in Twenty via the Person's company association. Any Cetec lead without an email address is flagged for manual review during reconciliation because Twenty's data model requires contact information to create a useful Person record.

Cetec Quotes with dollar-value, PPV, and LBV approval thresholds migrate to Twenty CRM Opportunity records. The quote total and line items migrate as typed Opportunity fields and line item records in Twenty. Approval threshold metadata (per-user and global limits) is preserved as a custom field group on the Opportunity and documented in the workflow handoff inventory for the customer's admin to re-implement as a manual review process in Twenty since there is no native approval workflow engine.

Cetec Sales Orders in open status migrate as Opportunities with the appropriate stage value. Historical completed orders migrate as Opportunities in a Closed Won stage with the original order date preserved. Dual-fulfillment lines (the same part number with both build-to-stock and build-and-ship on one order) are parsed into separate line item records in Twenty, since Twenty's standard order model treats each part as a single line. We flag these during transformation so the customer's admin can verify the correct representation.

Cetec Part records (the central master record driving BOMs, inventory, and purchasing) migrate to a Twenty CRM custom object named 'Part' that we pre-create before import. Part number, description, unit of measure, and vendor pricing fields map to typed custom fields. Attachments (prints, spec sheets) export from Cetec as files and are attached to the corresponding Part custom object record in Twenty via the standard attachment model. This requires the Part custom object to be fully provisioned with all custom fields before Parts data import begins.

Multi-level BOMs with materials, work instructions, and sub-assemblies cannot map directly to any standard Twenty CRM object. We export the BOM structure as a structured JSON document and store it as an attachment on the corresponding Part custom object record. The BOM hierarchy (parent part, sub-assemblies, quantities, operations) is preserved but requires manual re-implementation in Twenty's custom object model or a companion MRP tool. We document the full BOM structure in the handoff inventory with field-level mapping.

Work Order records tie production scheduling, labor tracking, and cost accounting together in Cetec. Twenty CRM has no native production scheduling or work order object. We export Work Order records (open and historical) as a structured data export and store the export file in a dedicated location within Twenty's document attachment model, linked to the corresponding Part custom object where possible. A written Work Order inventory with all operation sequences, labor entries, and cost data is included in the handoff package.

PO records, line items, and receipt history export from Cetec and map to a custom Purchase Order object in Twenty that we pre-create before import. PO status, vendor, and line item details migrate with vendor name resolved to a Company record. Drop-ship PO patterns (where a PO auto-generates from a sales order) are flagged separately in the mapping notes because they create linked records in Cetec that require manual reconstruction in Twenty's object model. PO approval workflows are included in the workflow inventory handoff.

Cetec Notes (logged against Customer, Lead, or Order records) migrate to Twenty CRM Task records. The note body, author, and timestamp migrate to the Task description, created-by user, and ActivityDate fields. Task assignment in Cetec maps to the assigned user in Twenty via email lookup. Notes logged against manufacturing records (Work Orders, Inspections) that have no corresponding CRM object in Twenty are attached to the related Part or Company record if a valid lookup exists, or flagged in the reconciliation report for manual placement.

Cetec User records, role definitions, and per-module permissions migrate to Twenty CRM User accounts. Role names differ across platforms, so we map by permission set rather than by role name. Shop floor users on Cetec's $25/user/month tier who do not use CRM modules may be provisioned as inactive users in Twenty or excluded from migration depending on whether they have CRM-touching records; this decision is made during scoping based on the user's record history.

Document Management attachments in Cetec (stored against Parts, BOMs, Work Orders, and quality records) export in their original file formats and are mapped to the corresponding Part custom object record in Twenty. Documents attached to Work Orders and Inspections that have no target object in Twenty are collected in a structured file archive and linked to the relevant Part record where applicable. The revision control metadata (version number, revision date, author) is preserved in a custom field group on the attachment.

Quality Codes configured system-wide in Cetec for Inspections, NCRs, and receiving do not have a native equivalent in Twenty CRM. We export the code tables and map them to a set of Twenty custom picklist fields on the relevant objects (Part, Purchase Order, Work Order custom objects). Code categories that have no target field in Twenty are documented in the quality code handoff inventory with the full code set, descriptions, and intended behavior for manual rebuild.