Migrate from Wiise to Dolibarr ERP

Wiise Customer master records map directly to Dolibarr Third Party entries with the Customer flag enabled. We map Customer name, primary address, contact phone and email, payment terms, credit limit, and currency settings. Wiise Custom Fields on Customer records migrate to Dolibarr extrafields fields on the llx_societe table. Wiise's multi-entity Customer records within the same Wiise subscription become separate Dolibarr Third Party entries with distinct company identifiers so that intercompany accounting can be re-established in Dolibarr's Accounting module.

Wiise Vendor cards map to Dolibarr Third Party entries with the Supplier flag enabled. Purchase terms, currency settings, and Vendor-specific dimensional cost-centre tags migrate as Dolibarr extrafields on the llx_societe table. We create the Vendor Third Party before any Purchase Invoice records to satisfy the socid foreign key constraint in Dolibarr's llx_commande_fournisseur and llx_facture_fourn table imports.

Wiise Items (stock items, non-stock items, and services) map to Dolibarr Product records. Item type (stock, service, assembly) maps to Dolibarr Product type. Unit cost, inventory posting groups, and warehouse location assignments migrate directly. Wiise's 2 decimal-place limit on custom Item decimal fields causes precision loss during import; we flag every affected field in the pre-flight mapping report so the customer can decide whether to store the value as plain text or accept the rounding.

Wiise's dimensional chart uses account codes with cost-centre, department, and location tags on every posting. Dolibarr's Accounting module uses a flat account code structure with separate dimension labels defined per accounting journal. We map the base account codes directly and create Dolibarr accounting Dimension labels (analytical axes) to carry the cost-centre, department, and location meaning. The customer must enable and configure the Accounting module in Dolibarr and define the dimension labels before the account import phase begins.

Outstanding Wiise sales invoices migrate as Dolibarr Customer Invoice records with status set to unpaid. We preserve invoice date, due date, remaining amount, currency, and line-item descriptions. The customer_id lookup resolves to the Third Party created in step 1. Invoice PDFs stored outside the API require manual download from Wiise before cutover.

Outstanding Wiise purchase invoices migrate as Dolibarr Supplier Invoice records with status set to unpaid. Due date, remaining amount, and currency preserve. The supplier_id lookup resolves to the Third Party created in step 2. We flag any multi-entity intercompany AP records for the customer to confirm which legal entity in Dolibarr should absorb the liability.

Wiise Job headers, task-level work breakdown, resource assignments, and billing information map to Dolibarr Project and Task records. Job-specific dimension tags migrate as Dolibarr extrafields on llx_projet to avoid schema conflicts. Billable flag and billing method from Wiise Jobs map to the Project's budget and revenue tracking fields in Dolibarr. We create Projects before importing related open AR invoices so that WhatId references resolve correctly.

Wiise Employee records (name, position, department, employment status, HR metadata) map to Dolibarr User entries in the Employee category. We migrate active and terminated employees. Where Wiise uses an employment start date and termination date, Dolibarr stores these in the User record's employee fields. The customer must enable the HR module (extra) in Dolibarr and configure the employee category before migration.

Wiise Fixed Asset records (acquisition date, cost, depreciation method, book value, location) migrate to Dolibarr Asset entries. We preserve depreciation schedules as-is and flag any assets still under depreciation at the migration date so that the customer's finance team can confirm the remaining book value in the destination. Dolibarr's Asset module must be enabled before this phase begins.

Wiise Custom Fields on 15 page types (Customer, Vendor, Item, Sales Header/Lines, Purchase Header/Lines, Job, Contact, Fixed Asset, Service Item, and production objects) migrate to Dolibarr extrafields columns on the corresponding llx_ tables. We extract and recreate each custom field with its original data type, default value, and list of values if applicable. Dolibarr requires the extrafields table structure to exist before data imports; we pre-create all extrafields before the data migration runs.

Wiise's multi-entity single-subscription model means all company entities share a database but are logically separate. We export each Wiise entity's books as a separate company unit. Each entity becomes a distinct Dolibarr Third Party with its own address, bank details, and fiscal identification. Intercompany balancing entries in Wiise are exported and flagged for the customer to re-establish as inter-company journal entries in Dolibarr's Accounting module after migration.

Wiise warehouse locations and bin-level quantity records per inventory item map to Dolibarr Warehouse entries. Each warehouse in Dolibarr gets an address and manager assignment. Item-warehouse quantity records migrate to Dolibarr's product_stock table linking Product to Warehouse. If the destination uses a single warehouse, we consolidate the quantities; if multiple warehouses are required, we create one per Wiise location.

Wiise Payroll is a priced add-on per active employee with Australian and New Zealand compliance configuration. Employee compensation history, pay runs, and superannuation contributions require migration of a separate data set scoped to the HR module (extra) in Dolibarr. We recommend HR team sign-off on employee-level records before import. The Dolibarr HR module must be installed and the employee category configured on Users before payroll data loads.

Wiise Premium-tier Bill of Materials, production orders, and routing work-centre assignments map to Dolibarr's BOM module. BOM line items, quantities per assembly, and routing operation sequences migrate as Dolibarr llx_mrp_production and llx_mrpBomLine records. Material Requirements Planning (MRP) results from Wiise do not migrate as structured data; we recommend running MRP fresh in Dolibarr post-migration.

Wiise does not expose a public API endpoint for binary document and attachment retrieval. We ask customers to use Wiise's built-in document export function to download invoice PDFs, purchase orders, scanned files, and other attachments manually before the cutover date. Downloaded files are uploaded to Dolibarr's /documents/ directory structure matching the original record type (invoices, supplier documents, products, projects). This step requires manual effort from the customer and is not automated by FlitStack AI.