Migrate from CREST ERP to Odoo ERP

CREST ERP Customer master records map to Odoo res.partner with partner_type set to 'customer'. Contact details, addresses, credit limits, and payment terms migrate directly. We use the customer code from CREST ERP as the partner's ref field and set the customer_rank to flag them as a customer-facing record. Custom properties attached to customers in CREST ERP are captured via database inspection during discovery and mapped to custom partner fields in Odoo or documented for Odoo Studio recreation.

CREST ERP Vendor master records map to Odoo res.partner with partner_type set to 'supplier'. Supplier details, bank information, and performance ratings migrate to the vendor's Odoo partner record. Purchase terms are preserved as purchase_cutoff and property_supplier_payment_term days on the partner. The vendor-supplied catalogue of items maps to Odoo's product.supplierinfo table linked to the vendor partner.

CREST ERP Items map to Odoo product.product (stockable, consumable, or service variants). SKU, description, pricing, and UOM migrate to product_template fields with the associated product_variant records. Multi-level BOM structures in CREST ERP require decomposition: we extract the parent-item relationship and component quantities, then create Odoo mrp.bom records with type 'normal' or 'kit' depending on the BOM type, plus the mrp.bom.line children. Odoo requires work center definitions for routed manufacturing; we document the routing requirements for the customer's Odoo administrator to configure before production orders run.

CREST ERP's chart of accounts maps directly to Odoo's account.account records. Account codes, names, account types (asset, liability, equity, income, expense), and cost center assignments migrate. We preserve the CREST ERP account code as the Odoo code field for reconciliation continuity. Intercompany account mappings and bank account structures are reviewed during the GL phase to ensure that CREST's bank-ledger-to-GL-account assignments translate correctly to Odoo's bank reconciliation configuration.

CREST ERP open AP records migrate as Odoo account.move records of type 'in_invoice', linked to the vendor res.partner. Invoice number, amount, due date, and payment state migrate with the vendor_invoice_id reference preserved. We identify which CREST ERP AP records remain open at cutover to avoid importing satisfied invoices. Odoo's account_payment register handles post-migration payment recording against these migrated bills.

CREST ERP open AR records migrate as Odoo account.move records of type 'out_invoice', linked to the customer res.partner. Invoice number, outstanding amount, and aging bucket migrate. We flag credit memos and partial payments for correct offset handling using Odoo's credit note pattern. The AR aging report is validated post-migration against the CREST ERP source to confirm totals match before go-live.

CREST ERP Sales Orders migrate as Odoo sale.order records with sale.order.line children. Customer linkage, line items, quantities, pricing, delivery dates, and order status migrate. CREST ERP SFA pipeline stages map to Odoo sale.order state (draft, sent, sale_order, done) with any custom stage status preserved as a custom field on the sale order for audit. Odoo's delivery integration (stock.picking) is triggered from confirmed sale orders after migration; existing fulfilled orders are migrated with delivery moves completed.

CREST ERP Purchase Orders map to Odoo purchase.order with purchase.order.line children. Vendor linkage, line items, quantities, pricing, expected delivery dates, and receipt status migrate. CREST ERP approval workflows on purchase orders are documented for Odoo purchase approval rules to be configured post-migration by the customer's admin. Incoming shipments linked to received POs migrate as stock.picking records with state set to done.

CREST ERP Fixed Asset records migrate to Odoo's account.asset records with acquisition cost, depreciation schedule, asset category, location, and maintenance history. Depreciation method and schedule from CREST ERP map to Odoo's fiscal depreciation entries. We generate asset.depreciation.confirmation.lines aligned with the original schedule so that the depreciation timeline is continuous from go-live.

CREST ERP Employee records migrate to Odoo hr.employee with personal details, job role, department, and bank details. Effective-dated compensation history requires sequencing: we migrate the most recent compensation record as the employee's current contract (hr.contract), and historical pay period entries migrate as payroll journal entries if Odoo Payroll is in scope, or as a compensation history note if not. Leave balances from CREST ERP map to Odoo's hr.leave.allocation records.

CREST ERP Department structure maps to Odoo's hr.department with department codes, names, and parent-child relationships preserved. We validate that cost center assignments on GL accounts align with the migrated department hierarchy during the GL migration phase. The organizational chart in Odoo is validated post-migration against the source.

CREST ERP Project records migrate to Odoo project.project with budget, resource assignments, tasks, milestones, and time entries. CREST ERP project templates require manual re-creation in Odoo as project templates because template portability between systems is not supported by the APIs of either platform. Time entries from CREST ERP map to Odoo account.analytic.line records linked to the project.