Migrate from Total Control Pro to Twenty CRM

Total Control Pro customer records map to Twenty CRM Company records for the organization and Contact records for individual points of contact. The customer's company name, billing address, and account terms migrate to Company. Named contacts (sales, purchasing, quality contacts per customer) migrate as linked Contact records with the Company as the parent. We use the customer account number as the dedupe key and flag duplicate company names for resolution before import.

Total Control Pro supplier records map to Twenty CRM Company records with a Company Type of 'Supplier' or 'Vendor' to distinguish from customer accounts. Supplier part supply links, lead times, and purchase item assignments migrate as custom fields on the Company or as a linked Custom Object for part-supplier relationships if the customer's data volume warrants it.

Total Control Pro product definitions (part numbers, descriptions, unit of measure) map to Twenty CRM Product if the customer's deployment uses the Products module, or to a Custom Object (e.g., 'Part Number') if the CRM is used to track manufacturing items rather than for sales quoting. We validate part numbers against the destination item list and flag duplicates for resolution.

Total Control Pro Work Orders migrate to a Twenty CRM custom object named WorkOrder (or equivalent per customer naming) defined via the /metadata API before import. The custom object includes fields for Work Order number, status, assigned operations, and timestamps. Operational history including any manual overrides logged by shop-floor staff migrate as activity records linked to the WorkOrder custom object. We sequence Work Orders by creation date to preserve the production timeline.

Total Control Pro BOMs with multi-level structures and revision numbers migrate to a Twenty CRM custom object BillOfMaterials. We identify the active BOM revision as of migration cutoff by querying the most recent approved revision per product and confirm it with your team during the discovery call. Component part numbers map to destination Product or Part Number records, and the BOM structure (parent-component relationships) migrates as a nested custom object or as JSON-serialized component list depending on the complexity. We flag BOM revision histories for manual review if the customer requires historical versions preserved.

Current stock levels, bin locations, and lot numbers migrate as a snapshot to a Twenty CRM custom object InventorySnapshot. Live inventory movements during the migration window are queued and replayed post-cutover to avoid discrepancy. If the customer requires ongoing inventory tracking in the CRM, we configure a scheduled update mechanism or recommend a dedicated inventory management integration post-migration.

Production scheduling data including operation sequences and due dates maps to Twenty CRM Task records (if treated as operational activities) or to a custom object ProductionRun (if a richer schema is required). We flag any constraint flags or priority overrides as custom fields on the migrated records. Scheduling data is imported after Work Orders to preserve the parent-child relationship.

Inspection results and non-conformance records migrate as linked child records under their parent Work Order custom object in Twenty CRM. Each Quality Check record carries the inspection date, result (pass/fail/non-conformance), and any linked non-conformance notes. We resolve the parent Work Order reference by Work Order number lookup during import.

MIM-derived KPIs (OEE, cycle time, scrap rates) stored as time-series in Total Control Pro migrate to a Twenty CRM custom object MIMetrics with date-bounded rows. We chunk the export into date-bounded batches to avoid export timeouts and normalize the data into a flat row format that maps to the custom object's fields. If the customer's BI or reporting tool is available, we deliver the data as a supplementary CSV alongside the transactional migration.

Total Control Pro user-defined fields added during implementation migrate to Twenty CRM custom fields on the equivalent mapped object. We enumerate all custom fields during the discovery call, identify their data types, and map them to the appropriate Twenty CRM field type (text, number, date, picklist, etc.). Custom field metadata is applied before record import so that data lands in the correct fields on first load.

Customer account management activities from Total Control Pro (review meetings, contract renewals, QBRs) migrate as Twenty CRM Task records linked to the Company record. We preserve the original activity date for timeline ordering and flag any tasks without a resolved parent Company for manual assignment post-import.