Migrate from Everwin to Dolibarr ERP

Everwin Customer records map to Dolibarr Third Parties (llx_societe). Customer name becomes nom, address fields map to address/zip/town/country, phone/email map to phone/email. The customer-supplier flag from Everwin sets fk_typent for third-party type classification. We export the full customer record with any custom fields and build a per-installation field map before import because Everwin's customer schema varies by installation.

Everwin Vendor records map to Dolibarr llx_societe records with the Supplier flag activated. Payment terms, bank details, and contact information map to corresponding Dolibarr fields (mode_reglement, bank_account). Vendor records are imported in the same batch as Customer records because they share the llx_societe table with a type discriminator.

Everwin Project records map to Dolibarr llx_projet with Project status from Everwin mapped to Dolibarr's status codes (0=draft, 1=open, 2=closed). Custom fields on Everwin Projects require extrafields mapping to Dolibarr extrafields configuration on the llx_projet table. Budget and billing information from Everwin migrates to llx_projet_task for task-level detail if present.

Everwin User accounts with roles and permissions map to Dolibarr llx_user. Email becomes login, role assignments map to the relevant Dolibarr permission flags (admin rights, project manager, HR reader). We export User records and map them before importing any record that carries an owner reference to ensure OwnerId resolution during subsequent imports.

Everwin invoices and purchase orders map to Dolibarr llx_facture (customer invoices) or llx_commande_fournisseur (supplier orders). Open AP/AR records migrate as live documents with status preserved. Fully paid or fully received historical transactions migrate as read-only journal entries in Dolibarr's accounting module to maintain balance continuity without creating active obligations.

Everwin document attachments (binary blobs) export with filename and parent entity reference. We transfer the binary files to Dolibarr's documents/ directory using the same folder structure and recreate the ECM entries (llx_ecm_files) with the correct parent entity type, ID, and file path. Binary format and storage location vary by Everwin installation, so we validate file integrity and Dolibarr MIME type compatibility during the export phase.

Everwin Item records with SKU, description, unit cost, and custom attributes map to Dolibarr llx_product. The Everwin SKU becomes product ref; description maps to label. Pricing migrates to the standard price book. Custom attributes require extrafields mapping on llx_product. Dolibarr's product variants module can accommodate size/color variations if the Everwin item schema supports variant definitions.

Everwin chart of accounts requires account code mapping to Dolibarr's accounting plan. We export the full account structure and present a reconciliation matrix for the customer to approve before loading. French PCG account codes map to standard Dolibarr accounting configuration with account type classification (actif, passif, charge, produit).

Everwin tax codes tied to French jurisdiction map to Dolibarr's TVA rate configuration (llx_c_tva). Each Everwin tax code requires a value mapping table referencing Dolibarr's supported rate list. French VAT rates (20%, 10%, 5.5%, 2.1%) and intra-EU rates map to Dolibarr's tax configuration. Reverse-charge mechanisms for cross-border transactions require specific mapping if present in Everwin.

Everwin custom objects have per-installation unique schemas. We introspect the schema during scoping, create corresponding Dolibarr extrafields definitions on the relevant base table (llx_socpeople, llx_projet, llx_product, etc.) or create a custom Dolibarr table if no base object fits. This is the most migration-specific work because no two Everwin installations have identical custom object structures.

Everwin Contact sub-records attached to Customer entities map to Dolibarr llx_socpeople. The contact is linked to its parent third party (llx_socpeople.fk_soc) during import. Email, phone, role/title, and address fields migrate directly. Multiple contacts per customer are supported in both systems.

Everwin engagement records that are notes or tasks map to Dolibarr llx_note for free-text notes attached to third parties or projects, and llx_actioncomm for scheduled or completed tasks. Timestamps and owner references are preserved. Email and call engagement records map to llx_actioncomm with appropriate type coding (AC_TEL for calls, AC_EMAIL for emails) if Everwin exposes these as distinct objects in the API.