Migrate from PrismERP to Dolibarr ERP

PrismERP Customer Master records (personal details, company data, contacts, addresses, banking information) map to Dolibarr ThirdParty objects with the Customer flag enabled. The dedupe key is email or customer code. We preserve address records as Dolibarr Address records linked to the ThirdParty, and contact persons as Dolibarr Contact records with a link to the parent ThirdParty. Payment terms and credit limits migrate as dictionary values in Dolibarr's TermsofPayment static table.

Vendor Master mirrors Customer Master structure in PrismERP. We map to Dolibarr ThirdParty with the Supplier flag enabled. Banking information (SWIFT, IBAN, account number) migrates as a Bank Account record linked to the ThirdParty. PrismERP vendor categories map to Dolibarr Categories (Suppliers type) for reporting segmentation.

PrismERP's hierarchical Chart of Accounts may include multi-segment dimension codes (company, region, department, product line) in a single account code. Dolibarr uses flat account codes (char 32 max) for its double-entry accounting. We generate a segment mapping worksheet during discovery, have the customer define how each PrismERP dimension maps to either Dolibarr account codes or cost center fields, and apply the transform as a pre-load step. Account types (Asset, Liability, Equity, Revenue, Expense) map to Dolibarr's pcmt_type values.

Open Accounts Receivable vouchers from PrismERP map to Dolibarr Customer Invoice records with status Draft or Unbilled. Open Accounts Payable vouchers map to Dolibarr SupplierInvoice records. Current outstanding amounts and due dates are preserved as invoice total and due date. The originating journal entries from PrismERP are loaded as Dolibarr AccountingEntry records (manual bookkeeping entries) to preserve the full audit trail for closed and open periods. Historical closed-period transactions are exported as a separate read-only file set for audit retention.

PrismERP Items (product definitions, pricing tiers, stock levels, warehouse assignments, BOM associations) map to Dolibarr Product records. Product type (stockable, service, assembly) is determined from PrismERP item type. Current stock quantities per warehouse import into Dolibarr Stock (Warehouse module) as stock movement records with today's date and the source reason 'Import'. BOM associations migrate as Dolibarr BOM records linked to the parent Product if the MRP module is enabled in the destination.

PrismERP SDM Purchase Orders (headers, line items, quantities, agreed prices, vendor assignments, approval status) map to Dolibarr SupplierOrder. PO line items map to SupplierOrderLine with Product reference resolved via SKU match, quantity, and unit price. Approval status from PrismERP becomes Dolibarr order status (Draft, Validated, Approved, Sent, Received) with a note preserved in the order description.

Sales Orders and related delivery and invoice documents from PrismERP SDM map to Dolibarr Order, then to Shipment and Invoice records depending on lifecycle stage. Line-item detail, pricing, customer linkage (ThirdParty lookup), and order status all migrate. The mapping preserves the order-to-invoice lineage so that Dolibarr's invoice can be generated from the imported order.

PrismERP Production Planning & Control orders (BOM references, routing steps, quantities) map to Dolibarr Manufacturing Order (MO) if the MRP module is activated. The production order header migrates with BOM linkage, planned quantity, and status. Routing steps are documented as a note attachment on the MO rather than as a structured routing record, since Dolibarr's basic MRP module does not support multi-step routing. Teams with complex production planning should treat this as a scope boundary and plan a separate MRP implementation review.

PrismERP HCM Employee records (personal data, employment details, department assignments, compensation history) are the highest-confidence data set in PrismERP based on user reviews. We map to Dolibarr User records for authentication plus Dolibarr Employee records (from the HRM module) for employment data. Department assignments map from PrismERP's organizational hierarchy to Dolibarr Departments. Compensation history is preserved as a Note attached to the Employee record since Dolibarr HRM does not have a native compensation history object.

PrismERP organizational hierarchy maps to Dolibarr Department records. We preserve the full department tree structure as parent-child Department relationships in Dolibarr. Cost center assignments on accounts and projects from PrismERP are mapped to Dolibarr's Categories (with Cost Center type) for use in accounting reports, since Dolibarr's basic accounting module does not have a native cost center dimension.

PrismERP Project System entries (project definitions, WBS elements, time entries, budget assignments) map to Dolibarr Project records. WBS elements migrate as Dolibarr Tasks with hierarchical parent-child relationships. Time entries map to Dolibarr ProjectTaskTime records if the Tasks and Timesheets module is enabled. Budget assignments require a manual reconciliation step because PrismERP and Dolibarr use different budget tracking models. Projects without tasks are imported as Project headers with a status flag set to 'Not started'.

PrismERP Document Management System files linked to transactions, master records, and projects are exported as binary files with their attachment metadata (original filename, file type, creation date, linked record ID). We load them into Dolibarr's Documents module as file attachments linked to the corresponding migrated record. The migration preserves the file association but not Dolibarr-native version history, which starts from the migration date. File types supported include PDF, Office documents, images, and CSV data files.