Migrate from Access SupplyChain to Dolibarr ERP

Access SupplyChain Customer records (name, contact details, payment terms, addresses, custom fields from Access Studio) map to Dolibarr ThirdParty records with the Tiers type set to Customer. We extract the customer code from Access SupplyChain as the ref (reference) field in Dolibarr, and the primary contact name becomes the Nom field. Address records map to Dolibarr's address fields (address, zip, town, country). Custom fields added in Access Studio are enumerated during discovery and mapped individually to Dolibarr ExtraFields on the ThirdParty module; unsupported data types (e.g., embedded objects) are flagged for customer approval before import.

Access SupplyChain Supplier records (name, address, bank details, category assignments) map to Dolibarr ThirdParty with Tiers type = Supplier. Bank details from Access SupplyChain transfer to Dolibarr's rib (bank account) fields. Supplier-to-customer relationship records (if maintained as a cross-reference in Access SupplyChain) require explicit mapping to Dolibarr's Category system or a custom relation table. Document attachments on supplier records migrate as Dolibarr document records linked to the ThirdParty.

Open and historical purchase orders from Access SupplyChain migrate to Dolibarr SupplierOrder (commande_fournisseur). Status values (Draft, Sent, Received, Closed) map to Dolibarr statuses (Draft, Validated, Received, Closed). Closed orders migrate as read-only history unless the customer requests them in open status. Line items on each purchase order map to SupplierOrderLine with Product reference, quantity, unit price, and tax rate resolved at migration time. If Access SupplyChain holds partial receipts against an order, we flag these for manual reconciliation in Dolibarr after import.

Access SupplyChain Item master records (SKU, description, unit of measure, cost price, sales price, type) map to Dolibarr Product. The Access SupplyChain SKU maps to Dolibarr's ref (product reference). Items flagged as stock-managed in Access SupplyChain activate the Dolibarr Stock module on the product record. Where items have been merged or archived in Access SupplyChain, we flag duplicates and apply a deduplication rule during scoping before import begins. Unit of measure (UoM) from Access SupplyChain maps to Dolibarr's unit_of_measure field; non-standard UoMs require custom configuration in Dolibarr before import.

Access SupplyChain warehouse records and bin locations migrate to Dolibarr Warehouse (entrepot). Stock-on-hand figures are extracted as a snapshot at cutover and applied as an initial stock balance in Dolibarr rather than as transactional stock movements, to avoid mid-migration discrepancies. If Access SupplyChain holds multi-location stock data (multiple bins per warehouse), we create one Dolibarr warehouse per Access SupplyChain warehouse and map bin locations into Dolibarr's location field, noting that Dolibarr's standard module does not have a native multi-bin picking system.

Access SupplyChain chart of accounts structures migrate to Dolibarr's accounting module (comptabilite) as Accounting Account records. Complex multi-company or multi-segment account codes require explicit mapping per legal entity during discovery. We do not assume a single unified account structure; scoping includes an account structure interview to map each entity's accounts to Dolibarr's account code format. If the customer uses Access Coins Evo's cost tracking accounts, we map those to Dolibarr's project cost accounting entries under the Project module.

Outstanding AP and AR invoices, credit notes, and partial payments migrate as open items in Dolibarr. We flag payments in transit and unresolved allocations to prevent double-posting at go-live. Outstanding invoice totals from Access SupplyChain are loaded into Dolibarr as unpaid invoices; the reconciliation worksheet we provide lists each open item with its Access SupplyChain reference, amount, due date, and counterparty so the customer's team can match and allocate in Dolibarr's banking module post-import. Any payments received or applied between export and go-live require manual review and re-application.

Access SupplyChain user accounts migrate to Dolibarr User records with their role assignments. Role naming conventions differ between Access SupplyChain versions and Dolibarr's permission system, so we map Access SupplyChain roles to Dolibarr permission groups (read, write, validate, admin per module) during scoping. If a user in Access SupplyChain has a custom role not directly representable in Dolibarr, we flag it for the customer's admin to configure post-migration.

Documents attached to suppliers, items, and purchase orders in Access SupplyChain are exported and linked to their Dolibarr destination records as document files under the appropriate module's document directory. We check file sizes and formats during scoping; very large files (over 50 MB) or non-standard formats may require a separate file transfer procedure. Dolibarr's document storage is directory-based, so we replicate the Access SupplyChain attachment folder structure in Dolibarr's htdocs/documents/ hierarchy.

Custom fields created in Access Studio are enumerated during discovery and mapped individually to Dolibarr ExtraFields. The Dolibarr ExtraFields system supports field types including varchar, text, int, double, date, datetime, boolean, select, multiselect, and link (foreign key). Fields with unsupported data types such as embedded objects or Access-specific binary types are flagged and handled per a customer-approved fallback (dropped, stored as text, or reviewed for custom Dolibarr extension development). We document the full custom field inventory and the mapping decision for each field before import begins.

If the customer uses Access Coins Evo for construction project cost tracking and supplier risk scoring, those records require evaluation against Dolibarr's Project module. Dolibarr's project management covers basic job costing, task tracking, and time allocation but does not have a native supplier risk scoring equivalent. We migrate project records and their cost line items as Dolibarr Projects with task-level cost entries; supplier risk scores are noted as a custom ExtraField on the relevant ThirdParty records. Coins Evo-specific AI-assisted forecasting data does not have a Dolibarr equivalent and is excluded from migration scope.

Access SupplyChain category assignments on customers, suppliers, and items map to Dolibarr Categories. We extract the category hierarchy from Access SupplyChain and create equivalent Dolibarr categories (type Customer, Supplier, or Product) with the same parent-child structure. Category-based reporting in Dolibarr references the category label rather than an ID, so label preservation is critical for reporting continuity.