Migrate from ABRA Gen to Odoo ERP

ABRA Gen firmy records contain address, contact, financial classification, and ICO (company registration number). We map these to Odoo Contact records with the ICO stored in the Odoo partner vat field as the Czech business identifier. Multiple firmy addresses map to Contact addresses with address_type (invoice, delivery, contact) set per ABRA Gen's address role. Any custom firmy extensions discovered during database schema inspection are flagged and mapped manually.

Customer master records in ABRA Gen (odberatele) mirror firmy structure with billing and shipping specifics. We map to Odoo Contact with customer_rank set to 1 and any ABRA Gen-specific payment term codes mapped to Odoo property_payment_term_id on the partner. Customer-specific discount structures preserved as custom fields on the partner record.

Vendor master records (dodavatele) map to Odoo Contact with supplier_rank set to 1. Banking details from ABRA Gen map to Odoo's bank accounts on the partner. Payment terms and vendor-specific conditions migrate to property_supplier_payment_term_id on the contact record. Vendor codes are preserved as the Odoo partner ref field.

ABRA Gen zakazky capture project-level financial tracking, billing, and cost allocation across job hierarchies. We map zakazky to Odoo Project records, preserving the job code as project name prefix and original zakazka number in a custom reference field. Nested job hierarchies are mapped to Odoo sub-projects via parent_id. Project financial data (budget, actuals) is stored as custom fields since Odoo Project does not natively carry accounting balances.

Product master records in ABRA Gen (vyrobky) include pricing, unit-of-measure definitions, and BoM structures. We map products to Odoo Product (product.product or product.template depending on variant complexity). Pricing migrates to list_price and standard_price. ABRA Gen unit-of-measure codes map to Odoo's uom.uom records with category matching. Multi-level BoMs require flattening: we map each ABRA Gen production route to either an Odoo phantom BoM (for kit-style structures) or a single-level BoM with component links.

ABRA Gen sklady records store warehouse codes, locations, and stock quantities. We map each sklad to an Odoo Stock Warehouse with the warehouse code preserved in warehouse.short_name. Inventory valuation methods (FIFO, average, standard) from ABRA Gen map to Odoo's product category valuation configuration (manual, average, real-time). Serial and lot-controlled items preserve lot_number and expiration_date in Odoo stock.lot records.

Czech accounting journal entries in ABRA Gen use specific COA structures and tax codes under Czech and Slovak fiscal law. We map ABRA Gen account codes to Odoo account.account codes with Czech chart of accounts template (Účtová osnova) applied. Document-level detail and audit trails preserve posting dates, fiscal year references, and tax analysis codes. Closed fiscal years are migrated as locked account.move records to satisfy Czech 5-10 year retention obligations.

Sales invoices, purchase orders, and delivery notes are stored in ABRA Gen as doklady headers with line items. We map vendor bills to Odoo account.move with move_type=in_invoice and customer invoices to move_type=out_invoice. Line items map to account.move.line with account, debit/credit, and tax_ids resolved from the ABRA Gen doklady tax configuration. Open documents migrate with date and invoice_date preserved; closed documents migrate as locked entries. Documents with posting dates outside the migration window are flagged for customer review.

Employee records from ABRA Gen include employment status, department assignment, and contact data. We map these to Odoo hr.employee with department_id resolved via name matching against Odoo hr.department records created during migration. Employment start date and employee code migrate to Odoo employee fields. Any HR-specific ABRA Gen extensions (attendance, leave balances) are flagged for the customer's HR team to configure in Odoo HR module post-migration.

ABRA Gen user accounts, roles, and permission sets map to Odoo res.users with login, name, and active status preserved. Role names from ABRA Gen map to Odoo access groups (res.groups) by name matching. Inactive ABRA Gen users are imported as inactive Odoo users to preserve historical assignment data without granting active login access. The customer's Odoo administrator reviews and activates users post-migration.