Migrate from Cetec ERP to Salesforce Sales Cloud

Cetec Customer records split into Salesforce Account (the company record) and Contact (the individual). The Account Name maps from Cetec customer_name, and the Account Site or Billing Address maps from Cetec address fields. We preserve the Cetec internal-customer flag in a custom Account field cetec_internal__c so that the company's own account is identifiable in Salesforce without relying on a locked editing constraint. Accounts are created before Contact import so that the AccountId lookup is satisfied at Contact insert time.

Cetec PQuotes map to Salesforce Opportunity with a note that approval thresholds (dollar-value, PPV, LBV limits per user and globally) have no native Salesforce equivalent. We preserve threshold metadata as a custom Opportunity field quote_approval_thresholds__c and deliver a written specification for rebuilding approval logic in Salesforce validation rules or Salesforce CPQ. If the customer licenses CPQ, Quote objects map directly. Quote line items map to OpportunityLineItem with unit price and quantity preserved.

Cetec Sales Orders map to Salesforce Opportunity. The Cetec order status (open, completed, cancelled) maps to Salesforce Opportunity StageName using a status-to-stage mapping defined during scoping. Cetec's dual-fulfillment pattern (build-to-stock and build-and-ship on the same part as two separate line items) requires reconstruction: we split the two fulfillment types into separate OpportunityLineItems with a custom fulfillment_type__c field set to build-to-stock or build-and-ship. Closed-Lost reason and Closed-Won reason from Cetec custom fields become Salesforce Loss Reason and custom Win Reason fields.

Salesforce has no native Purchase Order object. We pre-create a custom Purchase_Order__c object with fields for po_number, vendor_account (lookup to Account), po_date, status, and line items via a related Custom Purchase_Order_Line__c object with product (lookup to Product2), quantity, and unit_cost. Drop-ship PO patterns with automatic PO generation are flagged as requiring a separate rebuild discussion since they represent a purchasing automation that does not map to standard Salesforce records.

Cetec Parts map to Salesforce Product2. The part number maps to ProductCode, description to Description, and unit of measure to a custom field unit_of_measure__c. Vendor pricing rules from Cetec export as a custom Part_Vendor_Pricing__c related object with vendor account lookup, cost, and lead time. Average or FIFO costing method from Cetec's inventory pricing documentation is stored as a custom field costing_method__c on Product2.

Multi-level BOMs with sub-assemblies, materials, and work instructions require schema design before migration because Salesforce has no native BOM object. We offer two strategies during scoping: a custom BOM__c parent object with BOM_Line__c child records (supporting unlimited nesting levels), or a flattened bundle model using Product2 with a custom bom_structure__c field. Phantom BOM items are flagged with a custom is_phantom__c boolean. The customer chooses the strategy based on whether the destination Salesforce org has existing manufacturing add-ons.

Cetec Work Orders tie production scheduling, labor tracking, and cost accounting together. Salesforce has no native Work Order object; we use Case with a Work_Order Record Type and custom fields for operation_sequence, labor_hours, and work_order_status, or we create a custom Work_Order__c object if the customer's Salesforce edition supports it and the scope warrants it. Open Work Orders migrate as open Cases; historical completed orders migrate as closed Cases with completion metadata preserved in custom fields.

Cetec Inspection records linked to parts, lots, and work orders with revision-controlled outcomes (pass/fail/conditional) require a custom Inspection__c object with fields for part lookup (Product2), lot_number, work_order_lookup (Case or Work_Order__c), inspector (User), inspection_date, outcome, and any conditional notes. The inspection revision metadata is preserved as a custom revision_number__c field. We map inspection codes from Cetec's quality code tables to picklist values in the destination.

Cetec NCRs link to parts, suppliers, and root-cause analysis with disposition actions and corrective action records. We create a custom NCR__c object with fields for ncr_number, part_lookup (Product2), supplier_lookup (Account), linked_inspection (Inspection__c), status, root_cause_description, disposition_action, corrective_action, and closed_date. NCR status values migrate to picklist values matching the Cetec NCR workflow stages.

Cetec Quality Codes are system-wide configuration tables for inspections, NCRs, and receiving. We export the code tables and map them to picklist values on the corresponding custom objects (Inspection__c, NCR__c, and a custom Receiving_Inspection__c object if applicable). Any Cetec quality code category without a direct destination equivalent is flagged as a gap during the scoping call and resolved before migration begins.

Cetec documents attached to parts, BOMs, work orders, and quality records export as files that we upload to Salesforce as ContentDocument records linked via ContentDocumentLink to the corresponding target record. Revision-controlled documents preserve version history through ContentVersion with version_number matching Cetec's revision label. Attached prints and drawings map to the related Product2 or custom manufacturing object.

Cetec user records map to Salesforce User by email match. The $25/user/month shop floor role is a licensing consideration: if shop floor employees need CRM read access (viewing work order status, inspecting quality records), we map them to Salesforce Platform licenses ($25/user/month) rather than full Sales Cloud licenses. If they need no CRM access at all, they are excluded from the user migration and remain outside Salesforce. Cetec role-based permission sets map to Salesforce Permission Sets defined during schema design.