Migrate from VIENNA Advantage to Dolibarr ERP

VIENNA Advantage Business Partner is a unified entity covering customers, vendors, and employees distinguished by role flags (IsCustomer, IsVendor, IsEmployee). We split Business Partners during extraction: organisations with IsCustomer or IsVendor flag map to Dolibarr ThirdParty; individuals and employees map to Dolibarr Contact, linked via the fk_societe (ThirdParty) foreign key. Role flags are preserved in Dolibarr as category assignments and a custom field va_role_flags__c for audit. Multi-entity organisations generate multiple ThirdParty records with a parent_id hierarchy replicated in Dolibarr's References/Contacts tab.

VIENNA Advantage Products map to Dolibarr Product (llx_product) with type differentiation: manufactured items with BOM linkage become Dolibarr product type '0' (product) with the BOM replicated via Dolibarr's MRP module; service items become type '1' (service). SKU (M_Product.SKU) maps to ref_customer and ref_supplier on Dolibarr Product. UOM, pricing tiers, and reorder points map directly to Dolibarr's price lists and stock thresholds. The relatively new Dolibarr manufacturing module (1-2 versions old) is used; customers with complex multi-level BOMs should validate BOM nesting depth during sandbox migration.

VIENNA Advantage Sales Orders map to Dolibarr Commande (sales order) and Purchase Orders map to CommandeFournisseur (supplier order). Order headers carry BusinessPartner_ID and DocumentNo; order lines carry Product_ID, quantity, unit price, tax, and warehouse assignment. Order status (Draft, Submitted, Invoiced, Closed) maps to Dolibarr Statut (statut) and FulfilmentStatus. We preserve the original order date and the ordered quantity vs delivered quantity split across Dolibarr's delivery ( Expedition) and invoice (Facture) records.

VIENNA Advantage AR/AP invoices map to Dolibarr Facture and FactureFournisseur. Invoice headers carry the BusinessPartner_ID, invoice number, invoice date, due date, and payment terms; line items carry Product_ID, quantity, unit price, and tax rate. Payment records link via the paysnip table (Dolibarr's payment-to-invoice linking). Partial payment matching is preserved through the payment amount and remaining balance fields. VAT treatment requires attention during mapping if VIENNA Advantage used multi-tax configurations.

VIENNA Advantage GL journal entries (AD_JournalEntry) map to Dolibarr's Accounting module if activated. Journal lines carry Account_ID (GL account), debit amount, credit amount, and dimension tags (cost centre, project). Dolibarr's accounting module is optional and must be enabled during Dolibarr module activation; we coordinate with the customer on whether historical GL data migrates to Dolibarr's accounting entries (comptapoint) or is archived for tax reference only. Large historical GL datasets are chunked by fiscal period to avoid import payload limits.

VIENNA Advantage warehouse records (M_Warehouse, M_Storage) map to Dolibarr Entrepot (warehouse) and Stock (llx_product_stock). On-hand quantity, reorder point, reorder quantity, and expiration date fields transfer to Dolibarr's stock table. Multi-warehouse organisations generate multiple Dolibarr Entrepot records with location-specific stock tracking. We flag expiration date handling: Dolibarr's lot/serial module (module stock批次) must be enabled and the expiration fields activated during Dolibarr configuration before inventory import.

VIENNA Advantage Projects map to Dolibarr Project (llx_projet) with phases, resources, billing rules, and time entries. Project status (WIP, Completed, Closed) maps to Dolibarr's public_status flag. Billable vs non-billable flags and hourly rates migrate to Dolibarr's Project/task cost fields. Subtask hierarchies require flattening during migration if Dolibarr's task model does not support equivalent nesting depth. Project financial tracking (budget vs actual) maps to Dolibarr's Budget module if enabled.

VIENNA Advantage Tasks attached to Projects map to Dolibarr Task (llx_projet_task) linked to the parent Project. Task fields (name, description, assigned user, start date, end date, estimated hours, actual hours, status) transfer directly. Task assignment resolves VIENNA Advantage's AssignedTo user to Dolibarr User by email match; unresolved assignments go to a reconciliation queue.

VIENNA Advantage DMS documents are stored with internal storage paths that encode module context and version history. We extract binary files separately from metadata (file name, document type, version, associated Business Partner, Order, or Project ID), then re-associate each document to its Dolibarr parent record using the appropriate Dolibarr upload mechanism for the target module. Failure to re-associate results in orphaned files with no contextual link. We reconstruct the folder structure using the VIENNA Advantage DMS path metadata to restore logical organisation.

Custom fields added via VIENNA Advantage's Canvas framework are stored per-module with type, required, and default-value metadata. We extract the full custom field schema alongside the data and map each to Dolibarr's ExtraFields (extra fields) table for the corresponding module. Field types are translated: VIENNA Advantage numeric and date types map to Dolibarr's varchar/int/datetime types; dropdown fields map to Dolibarr's select/checkbox types. Custom fields on Dolibarr modules not covered by ExtraFields (e.g., on BOM or MRP) may require custom PHP development outside standard migration scope.

VIENNA Advantage Employees are stored as Business Partners with IsEmployee=true. These split into Dolibarr User records (login credentials and system access) and Dolibarr Member records if the HR/Members module is enabled. Employee attributes (department, job title, manager hierarchy) map to Dolibarr User properties and the Members module's profile fields. Compensation and payroll data does not migrate; VIENNA Advantage Professional tier payroll capabilities have no equivalent in standard Dolibarr and require separate evaluation.

VIENNA Advantage workflow definitions are declarative rule configurations tied to module context with no documented export format. We do not migrate Workflows as code. We capture screenshots and configuration notes of every active workflow during discovery, then deliver a Workflow Reconstruction Handbook mapping each VIENNA Advantage workflow trigger, conditions, and actions to Dolibarr BPM equivalent configurations. The customer's Dolibarr administrator or implementation consultant rebuilds approval chains manually using Dolibarr's workflow module if available or third-party workflow tools.