Migrate from Total Control Pro to Salesforce Sales Cloud

Total Control Pro Work Orders carry status, assigned operations, and timestamps with a full operational history including manual overrides logged by shop-floor staff. Salesforce has no standard Work Order object in Sales Cloud; we pre-create a custom Work_Order__c object with fields for wo_number (External ID), status, operation_sequence, assigned_workstation, start_date, completion_date, quantity_ordered, quantity_completed, and customer_reference. We resolve the parent Work Order lookup on child Operation_History__c records during import.

Total Control Pro BOMs are multi-level structures with revision numbers. Salesforce has no standard BOM object, so we create a parent Bill_of_Materials__c record with fields for bom_number, revision, product_name, status, and effective_date, and a child BOM_Line__c object with lookup to the parent BOM, component_part_number, quantity_per, operation_sequence, and workstation. We identify the active revision as of migration cutoff by querying the most recent approved revision per product and confirm it with your team before mapping.

Total Control Pro Product definitions (part numbers, descriptions, unit of measure) map to Salesforce Product2. The part number becomes ProductCode. We validate against the destination Product2 list and flag duplicates for resolution. If your Salesforce org uses a Pricebook for work-order costing, we create StandardPricebook entries during migration.

Total Control Pro inventory stores current stock levels, bin locations, and lot numbers. Since inventory is a live-moving target during migration, we extract it as a snapshot at cutoff. We create a custom Inventory_Snapshot__c object with fields for product (Product2 lookup), quantity_on_hand, bin_location, lot_number, last_updated, and warehouse. We do not migrate live inventory movements during migration; we queue and replay those post-cutover to avoid discrepancy.

Total Control Pro customer records with contact details, account terms, and associated sales orders map to Salesforce Account (company-level) and Contact (individual contact-level). The Total Control Pro customer address and payment terms map to Account fields. We flag any customer-specific design specifications stored on the customer record for migration to a custom field on Account or Contact.

Total Control Pro supplier records include part supply links and lead times. We map these to Salesforce Account records using a Supplier Record Type to distinguish them from customer Accounts. Purchase item assignments migrate to a custom Supplier_Item__c junction object linking the Account to the relevant Product2. Lead time data maps to a custom lead_time_days__c field on the junction object.

Total Control Pro production schedules include operation sequences and due dates. We map these to a custom Production_Schedule__c object with fields for schedule_reference, work_order (lookup to Work_Order__c), operation_sequence, scheduled_start, scheduled_end, priority_flag, and constraint_notes. Priority overrides and constraint flags are preserved as custom fields.

The MIM stores OEE, cycle time, scrap rate, and other operational KPIs as time-series data in a proprietary format. We extract these through a targeted MIM module export, normalise rows into structured records, and map them to a custom MIM_KPI__c object with fields for kpi_type, metric_value, recorded_date, shift, workstation, and related_work_order. For histories exceeding one million rows, we use Salesforce Big Objects to maintain performance.

Total Control Pro supports user-defined fields added during implementation. We enumerate all custom fields during discovery, classify their data type, and pre-create matching custom fields on the relevant Salesforce object before migration. Custom field values then migrate as standard field data rather than requiring a separate custom object.

Total Control Pro inspection results and non-conformance records are migrated as child records under their parent Work Order or Production Run. We create a custom Quality_Check__c object with fields for check_type, result (pass/fail), non_conformance_description, detected_date, and related_work_order lookup. Non-conformance flags map to a custom non_conformance_flag__c checkbox on Work_Order__c.

Total Control Pro document attachments (drawings, SOPs, inspection images) are stored in the platform's own file store and do not expose a documented export endpoint. We flag these for manual transfer using the platform's built-in export utility if available, or document the file inventory so your team can transfer them post-migration. Salesforce ContentDocument and ContentVersion objects are available to host the transferred files once migration is complete.

Total Control Pro workflow automation rules and third-party integration configurations are not exposed via a documented API. We cannot extract them programmatically. We deliver a written inventory of each integration (Xero, Dynamics 365 Business Central, HubSpot Sales Hub, Celonis) and automation rule with its trigger conditions, actions, and connected systems, so your admin rebuilds them in Salesforce Flow or through AppExchange integration apps post-migration.