Migrate from Total Control Pro to Pipedrive

Total Control Pro stores customer records with company name, contact name, delivery address, invoice address, and account terms. We split each record into a Pipedrive Organization (the company entity) and a Pipedrive Person (the named contact) linked via the Organization relationship. Email address is the primary deduplication key; records without email are held for manual resolution. Customer-specific designs and specifications stored as custom fields migrate as Pipedrive custom fields on the Organization record.

Supplier records in Total Control Pro include supplier name, contact information, part supply links, and lead times. These map to Pipedrive Organizations of type 'Vendor'. Lead time and part-supply associations migrate as custom fields on the Organization record. If Total Control Pro stores a per-supplier contact person, that person is added as a linked Person record under the Vendor Organization.

Total Control Pro Product records include part number, description, unit of measure, and cost price. These map to Pipedrive Products with Standard Price Book entries. The part number from TotalControlPro becomes the Pipedrive Product code. Pricing in Pipedrive Products reflects the sell price; if Total Control Pro stores only cost price, we flag the field for the customer's admin to set the selling price before the product is activated in Pipedrive.

Total Control Pro customer orders and quotes carry a status, a total value, and a reference to the customer and product. We map open customer orders to Pipedrive Deals with the deal value set from the order total, the Person and Organization linked from the customer record, and the pipeline stage set to 'won' or 'lost' based on the order status. Historical closed orders migrate with a closed date rather than as active pipeline entries. The order reference number becomes a custom field on the Deal.

Work Orders in Total Control Pro carry operational status, assigned operations, and timestamps but have no Pipedrive equivalent object. We extract the Work Order number, status, customer reference, product, and last-modified timestamp as a structured Note attached to the linked Pipedrive Organization (the customer) or Deal (the sales order). This preserves the work order context in the CRM without misrepresenting operational data as sales data. Active work order status flags can be set as custom field values on the Organization for at-a-glance reference.

Total Control Pro custom fields added during implementation vary per customer deployment. We enumerate all active custom fields during discovery, classify their data types (text, number, date, picklist, boolean), and pre-create matching Pipedrive custom fields on the corresponding object before migration. Picklist-type custom fields require explicit value mapping between Total Control Pro options and Pipedrive dropdown options.

Total Control Pro document attachments (drawings, SOPs, inspection images, customer-specific specifications) are stored in the platform's file store without a documented export endpoint. We flag these for manual transfer and provide a file inventory listing the record ID, file name, and file type for the customer's admin to handle via direct vendor cooperation or manual download. Attachments are excluded from the automated migration scope.

Bills of Materials in Total Control Pro carry multi-level component structures and revision histories that have no equivalent in Pipedrive's data model. BOM data is excluded from migration scope. If the customer requires BOM context in Pipedrive for sales engineering or configure-to-order scenarios, we recommend a separate product configuration integration built post-migration using Pipedrive's API and a third-party product configuration tool.

Current stock levels, bin locations, lot numbers, and live inventory movements are manufacturing-specific data with no Pipedrive equivalent. We exclude inventory data from migration scope. A snapshot of current stock levels can be delivered as a structured CSV alongside the CRM migration if the customer requires it for reference purposes.

The MIM stores OEE, cycle time, scrap rates, and other operational KPIs in a proprietary time-series format not exposed in standard exports. We exclude MIM KPI data from CRM migration scope. If the customer requires operational analytics in Pipedrive, KPI data can be surfaced via Pipedrive's custom reporting and Insights feature using custom fields on Deals or Organizations, but the source KPI extraction must be scoped separately from the CRM migration.