Migrate your De Facto ERP data

Customer records are standard master-data objects in De Facto's Financials and CRM modules. We map customer name, contact details, addresses, and account balances 1:1 into destination systems. Payment terms and credit limits require explicit field mapping due to variance between ERP conventions.

Vendor master records including addresses, payment terms, and bank details export cleanly. The platform supports multi-country supplier management; we preserve currency and tax code assignments during migration.

Items are the core of De Facto's supply chain module. Stock items, BOMs (bill of materials), and landed cost components (freight, insurance, duty, tax) require careful mapping — each item may have variable cost structures that destination systems handle differently. We extract items with all associated cost layers explicitly.

Open invoices, credit notes, and outstanding balances must be migrated with their payment status intact to avoid double-billing or reconciliation gaps. De Facto tracks these at the transaction level; we map open items by document date, due date, and remaining amount.

The chart of accounts is a standard master-data export. De Facto generates structured data output via TSQL scripts including CSV and XML formats, which we use for clean account structure extraction. Tax codes and department/cost center assignments require mapping to destination conventions.

User records and role assignments determine who can access what in De Facto. Role definitions are often highly custom and may not map 1:1 to destination permission models. We extract all users with their assigned roles and note where custom permissions require manual reconfiguration in the target system.

De Facto stores documents by default and links them to associated data records. Inbound documents can be auto-stored through OCR processing with barcode/QR reading. Document-to-record linkages and embedded documents in system-generated PDFs (SSRS-based) require explicit extraction work; we preserve document binaries and their source record associations separately from the data migration.

Full transaction history including purchase orders, sales orders, and warehouse movements can be exported via De Facto's TSQL script output. Large transaction volumes may require chunked extraction; we map each transaction type to its destination equivalent and preserve audit trail timestamps.

Fixed asset registers including acquisition cost, depreciation schedules, and asset locations export from the Financials module. De Facto's landed cost tracking for imported items may overlap with fixed asset cost components; we separate these concerns during mapping to avoid double-counting.

The CRM module includes opportunity tracking and contact management. We map opportunity name, value, stage, and associated contacts 1:1 where the destination is a CRM-capable system. Custom CRM fields require field-level mapping work.

De Facto's Reporting & Analysis (BI) module uses Microsoft SSRS-based report definitions. Report templates and SSRS configurations are not portable across platforms; we export the data that feeds reports but not the report definitions themselves. Customers should rebuild reports in their destination BI tool.