Migrate from Total Control Pro to Microsoft Dynamics 365 Sales

Total Control Pro Customer records map to Microsoft Dynamics 365 Sales Account. Customer name becomes Account Name; contact details split into Account phone and address fields. We preserve the original customer ID as a custom field tcp_customer_id__c for reconciliation. Account terms (payment terms, credit limits) from Total Control Pro migrate to a custom field or Note attached to the Account record.

Primary contact on each Total Control Pro Customer record maps to a Microsoft Dynamics 365 Sales Contact. Contact name, email, phone, and role transfer directly. If Total Control Pro stores multiple contacts per customer, we create additional Contact records linked to the same Account via the parentcustomerid lookup. The primary contact is flagged with a custom field tcp_primary_contact__c set to true.

Total Control Pro Products (part numbers, descriptions, unit of measure, standard cost) map to Microsoft Dynamics 365 Sales Product2 records. The part number from Total Control Pro becomes Product2 Product Number; description becomes Description. Unit of measure migrates to a custom field or the Quantity Schedule. Standard cost becomes Current Cost on the Product2. We validate against any existing Product2 records using part number as the dedupe key.

Total Control Pro Bills of Materials have multi-level structures with revision numbers. Microsoft Dynamics 365 Sales has no native BOM concept. We create a custom BOM object with fields for bom_id, parent_part_number (lookup to Product2), component_part_number (lookup to Product2), quantity_per, and revision_number. The active BOM revision at migration cutoff is identified by querying the most recent approved revision per product and confirmed with the customer's manufacturing team before mapping. Historical BOM revisions are stored as separate BOM records with a revision_date field for audit.

Open Work Orders in Total Control Pro that represent committed or forecast production revenue map to Microsoft Dynamics 365 Sales Opportunity. Work Order number becomes Opportunity Name; expected completion date becomes Close Date; estimated production value becomes Amount. Work Order status (Released, In Progress, Completed) maps to Opportunity Stage (Qualification, Proposal/Price Quote, Closed Won). Closed Work Orders are not migrated as Opportunities unless they represent historical revenue that the customer wants visible in the CRM for reporting.

For customers who need full Work Order traceability inside Microsoft Dynamics 365 Sales , we create a custom Work Order object with fields mirroring the Total Control Pro schema: work_order_id, status, assigned_operations, expected_start_date, expected_completion_date, and estimated_value. Operations from the work order routing map to related custom Work Order Operation records. This is a configuration-heavy scope requiring pre-creation of the custom schema before migration.

Total Control Pro inventory snapshots (current stock levels, bin locations, lot numbers) are time-point data that do not belong in a CRM's transactional model. We create an Inventory Snapshot custom object with fields for product (lookup to Product2), quantity_on_hand, bin_location, lot_number, and snapshot_date. Live inventory movements during migration are queued and replayed as a final delta import post-cutover to avoid discrepancy at go-live.

Total Control Pro Suppliers map to Microsoft Dynamics 365 Sales Account records with a custom field tcp_supplier_type__c set to Supplier. This allows the customer to maintain a unified Account list covering both customers and vendors, with filtering by type for reporting. Supplier-specific fields (lead time, supply part links) migrate to custom fields on the Account.

Total Control Pro user-defined fields added during manufacturing implementation are enumerated during discovery and mapped to Microsoft Dynamics 365 Sales custom fields on the equivalent standard or custom object. Field type mapping follows Dynamics 365 type conventions (text to Single Line of Text, numbers to Whole Number or Decimal, dates to Date Only or Date Time). Custom fields are pre-created in Dynamics 365 before any record migration begins.

The Manufacturing Intelligence Module stores OEE, cycle time, and scrap rates as time-series data in a proprietary format. We extract the MIM export, normalize the rows into a date-bounded KPI dataset, and create a custom MIM KPI object with fields for product (lookup to Product2), kpi_type (OEE, cycle_time, scrap_rate), value, unit, and measurement_date. This is delivered as a structured migration into Dynamics 365 for BI consumption via Power BI rather than as native CRM records.