Migrate from ABRA Gen to Dolibarr ERP

ABRA Gen firmy records map to Dolibarr llx_societe (third-party) with separate llx_socpeople entries for individual contacts. Address, VAT number, customer/supplier classification, and payment terms migrate to Dolibarr's corresponding fields. The firmy financial classification (customer type, credit limit) maps to Dolibarr's code_client, code_fournisseur, and statut fields. Custom firmy extensions identified during schema discovery require manual field mapping and customer review before load.

ABRA Gen odberatele are a subset of firmy flagged as customers. We filter firmy by the customer classification property and load only those records into llx_societe with client = 1. Billing and shipping addresses migrate to llx_societe_rib for payment banking details and to llx_element_contact for address association.

ABRA Gen dodavatele map to llx_societe with supplier = 1. Vendor-specific fields including payment terms, vendor code, and banking details migrate to llx_societe_rib. Vendor-specific discount structures are preserved in a custom field or the local VAT identifier field depending on usage.

ABRA Gen zakazky capture project-level financial tracking, cost allocation, and contract billing. We map zakazky to llx_projet with the project code preserved as ref, the customer reference resolved to a llx_societe lookup, and any financial budgets carried into the budget fields. Nested zakazky hierarchies are flattened with a parent-child project structure using the father_id field.

ABRA Gen sklady map to Dolibarr llx_entrepot. Warehouse codes, physical addresses, and manager assignments migrate. Stock quantities per warehouse map to llx_product_stock after the product import is complete. Dolibarr's multi-warehouse support is activated during installation before migration begins; if ABRA Gen uses multiple storage locations within a single warehouse, we create separate Dolibarr warehouse records and document the consolidation decision.

ABRA Gen vyrobky (products, raw materials, services) map to Dolibarr llx_product with product type (product vs service) determined by the ABRA Gen item type field. Pricing migrates to llx_product_price and llx_product_price_level; unit-of-measure definitions map to Dolibarr's unit of measure fields. Multi-level BOMs (Bill of Materials) from ABRA Gen require scoping: we map them to Dolibarr's llx_product_bom for the optional MRP module, but complex multi-level BOMs may require flattening or manual reconstruction.

ABRA Gen doklady include sales invoices, purchase orders, and delivery notes stored as document headers with line items. We map open documents (unpaid invoices, pending purchase orders) to llx_facture (customer) or llx_facture_fourn (supplier) and llx_commande. Historical closed documents are scoped based on the legal retention period for the customer's jurisdiction; we recommend exporting closed fiscal years as read-only PDF archives rather than loading them into Dolibarr to avoid bloating the live system.

Czech accounting journal entries from ucetni require chart-of-accounts mapping to Dolibarr's llx_accounting_account table. We extract the source account codes, map them to the destination COA using a customer-supplied mapping table or a Czech statutory COA template, and load to llx_accounting_movent linked to llx_accounting_move. Account numbers, labels, and group hierarchies migrate; debit/credit amounts and currency codes are preserved directly. Any posting dates outside the migration window are flagged for customer review.

ABRA Gen user accounts, roles, and permission sets map to Dolibarr llx_user. Login, name, email, and active status migrate. Role and permission mapping is recorded in a written document for the customer's admin to reassign Dolibarr permission profiles (RH/HR manager, sales manager, accountant, etc.) post-migration because Dolibarr's permission model uses a flat profile system rather than ABRA Gen's module-level role grants.

ABRA Gen zamestnanci (employee records) for internal staff map to llx_user with employment status, department, and contact data preserved. External contractors or freelancers who are ABRA Gen suppliers or customers map to llx_societe with the employee flag recorded. HR and payroll-specific fields that have no Dolibarr equivalent are documented in a supplemental export for the customer's HR team.

ABRA Gen implementations frequently include custom-developed modules or heavily customized standard modules that are not documented in a machine-readable format. We identify custom objects during discovery by inspecting the live database schema against the standard ABRA Gen data dictionary. Each custom object is assessed individually: standard-mapping objects are mapped to Dolibarr llx_extrafields (extra fields on standard objects) or to a custom Dolibarr table; complex custom modules that exceed Dolibarr's schema flexibility are flagged as outside standard migration scope and documented for the customer.

Multi-level BOMs from ABRA Gen's vyrobky require scoping before migration. Dolibarr's llx_product_bom table supports single-level BOMs natively; multi-level BOMs may require flattening into a single assembled product or manual reconstruction in Dolibarr's MRP module. We document the full ABRA Gen BOM hierarchy during discovery, map what is migratable, and flag any levels requiring manual rebuild. The MRP module must be installed and activated in Dolibarr before BOM data is loaded.