Migrate from Accura to Odoo ERP

Accura Customer records map to Odoo res.partner with partner_type set to 'contact' for billing entities and 'invoice' for separate invoice addresses. The customer name, billing address, shipping address, phone, email, and payment terms migrate as standard fields. We apply a dedupe check on email and company name before insert to flag duplicate partners for customer review. Tax identification numbers from Accura map to Odoo's vat field if present in the export.

Accura Job records carry print-specific data (press type, sheet size, ink coverage, finishing operations) that requires a split migration strategy. The job header (customer reference, quote number, due date, job status) migrates as an Odoo sale.order with the partner_id resolved from the Customer mapping. Line items (print quantity, paper stock, artwork specs) migrate as sale.order.line records. If the print shop tracks production internally, the job also generates an mrp.production order for shop floor scheduling; otherwise, it maps to a stock.picking for fulfillment tracking. Print-specific attributes (press type, run size, imposition) require custom fields on sale.order or a product template variant structure we configure during schema design.

Accura Inventory Items map to Odoo product.product for stockable items and product.template for the product definition. We preserve the SKU (mapped to product.default_code), product name, unit of measure, cost price (mapped to product.standard_price), and quantity on hand via stock.quant records created after the product template is inserted. Items with zero quantity or negative balances are flagged in a pre-import review report for customer disposition before production migration.

Accura Invoices map to Odoo account.move with move_type set to 'out_invoice' for customer invoices and 'out_refund' for credit memos. Open invoices migrate with state set to 'draft' for review before posting; paid invoices migrate with state set to 'posted' and the payment reconciled via the invoice reference number matched against bank statement entries or manual payment records. Tax handling requires mapping Accura's tax codes to Odoo's tax tags and tax groups during the field mapping phase.

Accura Vendor records map to Odoo res.partner with the supplier flag set to True. Vendor name, contact info, payment terms, and bank details migrate to the partner record. We apply a duplicate-name check against existing vendor records before insert. If Accura tracks vendor-specific pricing for inventory items, we create product.supplierinfo records linking the vendor to the mapped product with the negotiated price and lead time.

Accura User records migrate as Odoo res.users with login set to the user's email address. Accura role and department assignments map to Odoo groups: the sale manager group for sales reps, stock manager group for warehouse staff, and account manager group for finance users. User passwords do not transfer; we set a temporary password and include a reset instruction in the migration handoff document. Inactive Accura users are flagged for the customer's admin to deprovision rather than migrate.

Custom fields on any Accura object (Customers, Jobs, Inventory, Invoices) export as additional columns in the CSV. We pre-create matching custom fields in Odoo before migration using the field type mapping (text to char, number to float or integer, date to date, checkbox to boolean). Fields that have no Odoo equivalent are flagged in a custom field inventory document for manual configuration in Odoo Studio or via Python code.

Accura Job line items (paper stock, ink, finishing, labor) map to Odoo sale.order.line with the linked sale.order as parent. Quantity, unit price, and description migrate directly. If Accura tracks cost vs. sell price per line, we preserve both in the sale.order.line record; the margin calculation happens in Odoo's standard reporting module post-migration.

Accura payment records against invoices map to Odoo account.payment entries reconciled with the corresponding account.move via the invoice reference number as the communication field. Partial payments create separate account.payment records with the remaining amount reflected in the account.move residual. We flag any payment records with missing invoice references for customer review before reconciliation.

Accura does not export job files, proofs, or documents via CSV. We provide a file location inventory document listing every attachment path referenced in the Accura database with its associated Job or Customer record, so the customer's admin can manually archive or migrate these assets to Odoo's document management module (ir.attachment) or an external storage location post-migration.