Migrate from EXACT to Pipedrive

Exact Contacts map to Pipedrive Persons. All standard fields including name, email, phone, job title, and address migrate directly. Exact's debtor/creditor flags are preserved as custom fields in Pipedrive since Pipedrive's Person object has no native financial classification construct for debtor or creditor classification.

Exact Organizations map to Pipedrive Organizations. Website, industry, and employee-count fields transfer directly. Exact's cost-center and financial-account linkages are stored as custom fields since Pipedrive's Organization object does not support ERP-linked attributes natively.

Exact Opportunities map to Pipedrive Deals. Deal name, value, stage, and expected close date transfer directly. Pipedrive's stage names are created to match Exact's pipeline stages during setup. ERP-linked line items from Exact's quote or invoice modules are stored as custom fields or notes since Pipedrive has no native ERP integration model for line items.

Exact activities (calls, emails, meetings) map to Pipedrive Activities. Original timestamps, activity type, and subject line are preserved. Exact's activity-linked ERP documents such as a call linked to a project are stored as custom fields since Pipedrive activities do not support document linkages natively.

Exact notes map to Pipedrive notes. Rich-text formatting is preserved where the export supports it. Notes attached to specific records in Exact are linked to the corresponding Person, Organization, or Deal in Pipedrive by reference during the import phase.

Any Exact custom fields on Contact records (e.g., 'sales_territory', 'product_interest') are created as Pipedrive custom fields on the Person object before migration. Pipedrive uses hash-based keys for custom fields, so FlitStack creates the field definition first and maps values during the import phase.

Exact Organization custom fields migrate as Pipedrive Organization custom fields. ERP-specific attributes such as 'warehouse_code' or 'fiscal_year_end' are recreated with matching field types (text, number, date, picklist) in Pipedrive during the pre-migration setup phase.

Exact users are matched to Pipedrive users by email address. Before migration, Pipedrive users must be provisioned (or invited) so records can be assigned to the correct owner. Unmatched owners are flagged and assigned to a fallback user for review.

Exact products map to Pipedrive Products. Product name, code, unit price, and description transfer directly. Exact's bill-of-materials or product variants are simplified to a single Pipedrive Product record per item; variant complexity is noted in the migration report for manual review and follow-up.

Exact workflows and automation rules cannot migrate to Pipedrive. FlitStack exports workflow definitions as a reference document (step-by-step logic, triggers, conditions) so your Pipedrive admin can rebuild them in Pipedrive's Automation builder. Automations tied to ERP events (e.g., invoice paid triggers a deal update) are not recreatable in Pipedrive's sales-focused model.

Exact deals often link to ERP documents including quotes, invoices, and purchase orders. Pipedrive has no ERP document model. We preserve document references as custom fields (e.g., 'exact_quote_id', 'exact_invoice_no') and attach the full document list as a note for manual follow-up and reconciliation.

Exact projects linked to opportunities are stored as custom fields on Pipedrive Deals using fields like 'project_id' and 'project_name'. Pipedrive has no native project object. Complex project-to-deal hierarchies are mapped as a note attachment with a reference table for manual resolution.