Migrate from eBIZ SMARTZ Business ERP to Dolibarr ERP

eBIZ SMARTZ Customer records map to Dolibarr Third Party (Societe) with customer flag enabled. The 360-degree customer view (consolidated orders, invoices, payments) maps to Dolibarr's linked contacts, proposals, orders, and invoices accessible from the Third Party page. Customer opening balances migrate as opening balance entries in Dolibarr accounting module.

eBIZ SMARTZ Orders map to Dolibarr Orders with order reference, date, and line items preserved. The transactional linkage to Customer migrates as the Third Party reference on the Order. Order status (pending, confirmed, shipped) maps to Dolibarr OrderStatus values. If the source uses order-to-invoice linkage, we preserve the reference for reconciliation.

Sales Invoices from eBIZ SMARTZ map to Dolibarr Customer Invoice records. Customer tax management from eBIZ SMARTZ (tax rates, tax codes) migrates to Dolibarr's VAT/revenue configuration. Invoice receipt status and payment linkage migrate to Dolibarr's payment status fields. Invoice knockoff and advance/refund deposit records map to Dolibarr's payment reconciliation features.

Payment records from eBIZ SMARTZ link to invoices via the Customer account and invoice reference. We migrate payment date, amount, payment method, and reference. Payments reconcile against the customer account balance in Dolibarr accounting module using the same reconciliation logic.

eBIZ SMARTZ multi-level chart of accounts maps to Dolibarr accounting module accounts. We preserve the account hierarchy levels (up to eBIZ SMARTZ's defined depth) as parent-child account relationships in Dolibarr. Inter-company segment information from eBIZ SMARTZ maps to third-party account links in Dolibarr rather than a dedicated intercompany segment. Opening balances for each account migrate as general ledger opening entries.

Historical journal entries and subledger transactions from eBIZ SMARTZ migrate to Dolibarr accounting entries with debit/credit preserved. We sequence entries chronologically to maintain audit trail integrity. Voucher posting and cancellation records from eBIZ SMARTZ map to Dolibarr's accounting entry reversal mechanism. Multi-level approval workflow metadata does not migrate; we document approval thresholds for admin rebuild.

eBIZ SMARTZ multi-level cost centers map to Dolibarr Projects. The hierarchical structure (categories containing cost centers) flattens to Dolibarr's project-parent relationship if within three levels; deeper hierarchies may require categorization into Dolibarr project categories. Project association from source orders and invoices migrates as project links on Dolibarr documents.

eBIZ SMARTZ corporate headquarters and division structures require restructuring for Dolibarr. If the destination organization uses Dolibarr's multi-company entity feature (paid module), each operating location maps to a separate Entity. Without multi-company enabled, divisions map to Projects with customer and order scope restricted per project. We determine the appropriate strategy during scoping based on reporting requirements.

eBIZ SMARTZ bank management records (cash transactions, bank transactions, inter-bank transfers) map to Dolibarr Bank Account entries. Cheque printing references migrate as bank transaction references. Bank reconciliation records from eBIZ SMARTZ map to Dolibarr's bank reconciliation feature with statement date matching.

Debit notes and credit notes from eBIZ SMARTZ map to Dolibarr Credit Notes (Avoir). The linked original invoice reference migrates as the source document link. Credit note amounts apply against customer account balances in Dolibarr accounting module.

eBIZ SMARTZ HR module employee records may map to Dolibarr Users if the HR module is in scope. Dolibarr's User model differs from HRIS; we typically migrate name, email, and Dolibarr permission profile. Historical compensation and benefits data from eBIZ SMARTZ HR does not have a direct Dolibarr equivalent and is documented in a written handoff for admin review or a separate HRIS migration.

eBIZ SMARTZ custom fields introduced during implementation require field-level mapping to Dolibarr extra fields (ExtraFields). Dolibarr supports extra fields on most standard objects as key-value pairs. We map each source custom field to a Dolibarr extra field with matching data type (text, date, numeric, select). Complex validation logic from custom fields does not migrate and requires manual Dolibarr configuration.