Migrate from Total Control Pro to Freshsales

Total Control Pro's Customers module stores contact records with delivery addresses, invoice addresses, quote-to-order references, audit trails, and nonconformance issues linked to the customer. We split this into Freshsales Contacts (the person) and Accounts (the company). The primary contact on the Total Control Pro customer record becomes the primary Contact in Freshsales; billing and delivery addresses migrate as Contact address fields and as a linked Account address. Any nonconformance history migrates as a custom field nc_history__c on the Account or as a Note attached to the Contact for audit trail preservation. Customers without a named company become Contact-only records in Freshsales.

Total Control Pro Product records (part numbers, descriptions, unit of measure, customer-specific designs, and specifications) map to Freshsales Products. The hs_sku equivalent migrates as Product Code. We validate each part number against the destination Product list and flag duplicates for resolution before import. Custom fields added during Total Control Pro implementation (custom product specifications, compliance codes, material grades) map to Freshsales custom fields on the Product object available from Growth tier onward.

Total Control Pro Supplier records include part supply links, lead times, and purchase item assignments. We migrate these as Freshsales Accounts with a custom field account_type__c set to 'Vendor' to distinguish them from customer Accounts. The supplier contact migrates as a linked Contact under the vendor Account. Purchase item assignments do not map to a standard Freshsales object; we store them as a structured Note on the vendor Account or as a custom multi-select picklist field for quick reference.

Total Control Pro supports user-defined fields added during implementation across Customers, Products, Suppliers, and Work Orders. We enumerate all custom fields during the discovery call, identify their data types, and map them to Freshsales custom field equivalents. Multi-checkbox fields map to Freshsales multi-select picklists; date fields map to date fields; numeric fields map to number fields with appropriate precision. Custom fields on Work Orders do not migrate because Work Orders have no Freshsales equivalent.

Total Control Pro Work Orders carry status, assigned operations, timestamps, and manual overrides logged by shop-floor staff. Freshsales has no Work Order or job management object. We document every Work Order record as a CSV export scoped to the migration date and deliver it alongside the CRM migration for the customer's admin team to assess for import into a dedicated ERP or job management system. The Work Order audit trail does not move into Freshsales CRM.

Total Control Pro BOMs store multi-level component structures with revision numbers and historical variants. Freshsales Products have no BOM sub-structure. We identify the active BOM revision at migration cutoff by querying the most recent approved revision per product and confirm it with your team. The BOM data (component part numbers, quantities, routing steps) is exported as a structured CSV and delivered for import into a manufacturing ERP or PLM system separate from Freshsales. BOM revision history is scoped explicitly during discovery because Total Control Pro does not automatically log which revision was active on any given past date.

Total Control Pro Inventory stores current stock levels, bin locations, and lot numbers. Freshsales has no inventory management capability. We export the inventory snapshot as of the migration cutoff date and deliver it as a CSV for import into the customer's warehouse management or ERP system. Live inventory movements during migration are queued and noted for manual replay post-cutover if required.

Total Control Pro's MIM stores calculated KPIs (OEE, cycle time, scrap rates) in a proprietary time-series format not exposed in standard exports. These metrics have no equivalent in Freshsales CRM. We extract MIM data through a targeted export scoped to the module, normalize the rows into a format suitable for BI ingestion, and deliver alongside the CRM migration. If the customer uses Freshsales reporting for pipeline metrics rather than manufacturing KPIs, the MIM data routes to a separate BI engagement.