Migrate from Accura to Dolibarr ERP

Accura Customer records with billing and shipping contact details map to Dolibarr Third-party records. Field mapping requires a column-level transform: Accura company name becomes Dolibarr's nom, address fields map to address and zip/town, phone and email map to phone and email. Duplicate-name handling in Dolibarr is enforced at the database level; we run a dedupe pass before insert using company name and email domain as the dedupe key. If the customer has both residential (individuals) and commercial (companies) records in Accura, we flag the Customer type for Dolibarr's Tiers type field (Customer, Supplier, or Both).

Accura Job records are the core entity in the print MIS. Active and in-progress jobs map to Dolibarr Commercial Proposals (Propal) for quote-stage records or directly to Orders (Commande) for confirmed jobs. Job line items map to ProposalLine or OrderLine records. We flag job status values that have no direct Dolibarr equivalent and map them to the closest ProposalStatus or OrderStatus value, with any untranslatable statuses noted in the handoff document. Job-level custom fields migrate as extrafields on the Proposal or Order object if Dolibarr's ExtraFields module is activated.

For print shops that use Jobs as project-level tracking entities with milestones and sub-tasks, we map to Dolibarr Project objects. Job status becomes ProjectStatus, and the job description maps to the Project notes field. Sub-jobs or job phases map to Dolibarr Tasks linked to the parent Project. The customer chooses the mapping strategy during scoping based on whether Accura Jobs function as quotes, active orders, or project folders.

Accura stock items and non-stock materials map to Dolibarr Product records. Quantity on hand migrates to the stock RealStock field if Dolibarr's Stock module is activated; cost basis maps to CostPrice. Items with negative balances or zero on-hand are flagged in the reconciliation report for customer review before insert. Print-specific items (paper stocks, ink codes, substrate types) retain their Accura SKU and description. Custom fields on inventory items (weight per sheet, grain direction, press compatibility) migrate as Dolibarr extrafields if the module is enabled.

Accura open invoices migrate to Dolibarr Invoice records with status = Draft for unpaid and status = Paid for settled invoices. Historical paid invoices migrate as read-only records for audit continuity. Invoice line items map to FactureLigne records with product reference, quantity, unit price, and VAT rate. We link invoice payments to bank records using Accura payment reference numbers where available. Invoice numbers are preserved in the ref field; if numbering sequences conflict with Dolibarr's configured format, we document the discrepancy and adjust the numbering sequence before migration.

Accura Vendor records map to Dolibarr Third-party records with Tiers type = Supplier. Contact name, payment terms, and address fields migrate directly. Vendor balances and terms are preserved in the payment condition fields. Duplicate-name handling runs against existing Third-party records to prevent supplier-customer duplication if both entities share a name in Accura.

Accura user accounts export with role and department assignments. We map these to Dolibarr User records. User passwords do not transfer—each user receives a password-reset link in Dolibarr after migration. Inactive Accura users are flagged for the customer to deprovision rather than migrate, avoiding license over-provisioning at the destination. If Accura role names do not match Dolibarr's permission groups, we map to the closest equivalent and note the gap in the handoff document.

Accura custom fields added to any object are exported as additional CSV columns. We carry each custom field into Dolibarr as an ExtraField entry on the matching object (Third-party, Product, Proposal, Invoice, or Project). Field type mapping: text fields map to varchar ExtraFields, numeric fields map to double, date fields map to datetime. Any custom field that lacks a matching target object or data type is flagged for manual Dolibarr configuration before the data import phase.

Proofs, job files, and documents stored inside Accura are not included in standard CSV exports. We provide a structured file-location inventory listing each job's associated documents, file path within Accura's storage, file type, and last-modified timestamp. The customer's team retrieves these files manually and uploads them to Dolibarr's document management area post-migration. We do not automate attachment transfer as the source file system is not accessible via API.

Accura payment records for settled invoices map to Dolibarr Payment records linked to the corresponding Invoice. Payment amount, date, and method (check, wire, cash) migrate to the Reglement table. We match payments to invoices using invoice reference and payment date. Any unmatched payment records are flagged in the reconciliation report for the customer's accounting team to resolve.

Accura job status values (e.g., Pending, In Production, Proofing, Shipped) map to Dolibarr status enumerations depending on the target object (ProposalStatus, OrderStatus, or ProjectStatus). We capture the full Accura status taxonomy during discovery and produce a status mapping table approved by the customer before migration. Any Accura statuses with no Dolibarr equivalent are documented with recommended custom status values the customer can add to Dolibarr's status lists.

Accura job line items map to Dolibarr line items on Proposals or Orders. Each line carries product reference, quantity, unit of measure, unit price, discount, and VAT rate. Print-specific attributes (paper grade, finishing type, quantity breaks) stored as separate columns in the Accura export are mapped to extrafields on the line item if Dolibarr's ExtraFields module is activated, or flagged for manual entry if the module is not in scope.