Migrate from Cetec ERP to HighLevel

Cetec ERP customers are unified entities with contact roles, billing addresses, and AR history. We split them into GoHighLevel Company records (the organization) and Contact records (the people). The primary billing address on the Cetec customer becomes the Company address; any named contacts with email or phone become Contact records linked to that Company via the Location relationship. We preserve the original Cetec customer ID in a custom field cetec_customer_id__c for audit and reconciliation.

Cetec ERP leads map to GoHighLevel Contacts with a Lead status custom field added. The lead's source, notes, and assigned sales rep migrate as Contact custom fields. If the lead has a linked customer (converted lead), we preserve that relationship through the Company mapping already established.

Cetec ERP quotes map to GoHighLevel Opportunities. The quote number becomes the Opportunity name; total dollar value migrates to the Amount field; line items (part number, quantity, unit price, extended price) migrate as Opportunity Line Items if GoHighLevel Products are used, or as a JSON-encoded custom field on the Opportunity if the part data does not map cleanly to a standard product model. Approval thresholds from Cetec (dollar-value, PPV, LBV) are preserved as custom fields on the Opportunity and noted for pipeline stage configuration.

Cetec ERP sales orders carry fulfillment status, line items, pricing, and customer linkage that GoHighLevel does not represent natively in a standard object. We create a Sales_Order__c Custom Object with fields for order number, customer link, order date, fulfillment status, and a JSON-encoded line items field. Historical orders migrate as completed records; open orders require a GoHighLevel workflow redesign to handle fulfillment tracking.

Cetec ERP parts have part number, description, unit of measure, vendor pricing, and revision level. The core product fields (part number as SKU, description, unit price) map to GoHighLevel Products. Manufacturing-specific attributes—revision-controlled documents, BOM links, vendor pricing rules, inspection requirements—do not map to a standard GoHighLevel Product and are stored in a Part_Attributes__c Custom Object linked to the Product.

Cetec ERP users with CRM access map to GoHighLevel users. The $25/user/month shop floor role in Cetec has no equivalent in GoHighLevel's per-user pricing model; we flag any shop floor users being migrated as full users so the customer can assess the pricing impact. Users are matched by email address; any Cetec user without a GoHighLevel equivalent is placed in a reconciliation queue.

Cetec ERP notes attached to customers, quotes, or orders map to GoHighLevel Notes linked to the corresponding Contact or Company via the related_to relationship. Note content, author, and timestamp preserve. Notes attached to manufacturing records (work orders, inspections, NCRs) do not have a destination in GoHighLevel and are flagged in the migration inventory for the customer's records.

Cetec ERP tasks linked to customers, quotes, or orders map to GoHighLevel Tasks. Task subject, due date, assigned user, and completion status preserve. We resolve the assigned user via the User email mapping established in the user migration phase.

Cetec ERP purchase orders have vendor, line items, receipt history, and drop-ship flags that GoHighLevel does not represent natively. We create a Purchase_Order__c Custom Object with fields for PO number, vendor link, order date, status, and line items. Drop-ship POs with automatic PO generation are flagged separately as they may create linked records requiring manual reconstruction in GoHighLevel.

Cetec ERP multi-level BOMs with materials, work instructions, and sub-assemblies have no GoHighLevel equivalent. We create a BOM__c Custom Object with fields for part number (lookup to Product), component parts, quantities, operation sequence, and a notes field. Multi-level nesting is flattened into a single BOM record with a parent-child relationship via a self-lookup or a separate BOM_Line__c object. Phantom BOMs are flagged for admin review.

Cetec ERP inventory quantities by warehouse with costing method (average, FIFO) have no GoHighLevel equivalent. We create an Inventory__c Custom Object with fields for part number (lookup to Product), warehouse location, on-hand quantity, and costing method. Live inventory levels are point-in-time snapshots; ongoing inventory tracking requires a separate ERP or inventory management system post-migration.

Cetec ERP documents attached to parts, BOMs, work orders, and quality records are exported as a file inventory with references to their parent records. GoHighLevel does not have a native document management system with revision control. We deliver the exported files as a ZIP archive organized by Cetec record type (parts, BOMs, quality) and a mapping CSV linking each file to its source Cetec record ID. The customer's admin rebuilds the document linkage manually or through a document management integration.