Migrate from Exact Globe to Odoo ERP

Exact Globe Accounts map to Odoo res.partner records with customer and supplier flags set independently. The Exact Globe account code becomes partner_ref in Odoo; the debtor/creditor classification maps to Odoo's customer_rank and supplier_rank integer counters. We extract parent-account relationships and map them to Odoo's commercial_partner_id for multi-company structures. Address, contact, and payment-term fields migrate directly with type-preserved field mapping.

The Exact Globe Chart of Accounts maps to Odoo's account.account model with account codes preserved as code values. Account groups from Exact Globe map to account.group for financial statement hierarchy. We extract account_type (asset, liability, equity, income, expense) and map to Odoo's accountType field. Account.reconcile flags and tax_ids require per-record configuration in Odoo before journal entries are loaded.

Exact Globe journal entries and their line items (split across separate tables) map to Odoo account.move records at the journal-entry level and account.move.line records at the line level. The Exact Globe journal code maps to account.journal selection (sale, purchase, general, bank, cash). Line-level dimensions (cost center, department) map to Odoo's analytic_account_id. Date-range scoping is agreed during discovery to exclude locked or reconciled periods.

Sales and purchase invoices from Exact Globe (header and line tables separated) map to Odoo account.move records of type out_invoice or in_invoice with corresponding account.move.line rows. Tax codes from Exact Globe require mapping to Odoo's account.tax records which must be pre-created in the destination. Payment terms, invoice status (open, paid, void), and due dates migrate with field-level mapping to Odoo's invoice_payment_term_id and amount_residual.

Exact Globe Items map to Odoo product.template with type (consu, service, product) and product.product variants created where Exact Globe has item variants. Item code becomes default_code; cost_price maps to standard_price; sales_price maps to list_price. Unit of measure from Exact Globe maps to uom_id in Odoo with a UoM conversion table for mismatched units.

Exact Globe BOMs with multi-level sub-assemblies require recursive traversal across pass-by-pass extraction because each level references child BOMs as separate records. We extract the top-level BOM first, then resolve component items (product.product ids) and quantities per mrp.bom.line. BOM type in Odoo (kits, normal, subcontract) is inferred from Exact Globe routing data. Operation routing (work centers, cycle times) maps to mrp.workcenter and mrp.routing.workcenter.

Exact Globe sales and purchase orders (split across header and line tables) map to Odoo sale.order and purchase.order records respectively with order lines migrated as sale.order.line and purchase.order.line. Order status (open, processed, invoiced, cancelled) maps to Odoo state (draft, sale, done, cancel). Back-order relationships from Exact Globe are preserved as sale.order.line linked to the original order via name pattern conventions.

Exact Globe Quotations map to Odoo sale.order records in draft state with quotation validity and expiration dates migrated. The conversion flag (expired, converted to order) maps to Odoo's state field and the presence or absence of an order reference. Line items migrate to sale.order.line with product mapping resolved against the product.template lookup.

Exact Globe Project headers with cost categories, billing methods, and budget data map to Odoo project.project linked to account.analytic.account for financial tracking. Project tasks migrate to project.task with planned hours, stage, and assignee mapping. Time entries from Exact Globe map to account.analytic.line records linked to the analytic account and the associated project.task.

Exact Globe HR records covering employee data, org structure, and effective-dated compensation map to Odoo hr.employee and hr.contract. Effective-dated compensation changes require careful sequencing during export to preserve historical salary records; each effective-dated row becomes a separate hr.contract with start and end dates in Odoo. Org structure maps to hr.department. Note that Odoo Payroll is an advanced module not included in all editions; we flag this during scoping and document the payroll rebuild scope for the customer.

Exact Globe Contact Persons linked to Accounts map to Odoo res.partner records with type=contact and parent_id pointing to the partner representing the Account. Name, role, email, phone, and address fields migrate directly. Contact lifecycle stage and ownership assignments map to custom fields on res.partner in Odoo. The email address is used as the dedupe key for duplicate detection during import.

Exact Globe Fixed Asset records with acquisition cost, depreciation method, book value, and asset class map to Odoo account.asset.asset and account.asset.category. Depreciation schedules require recalculation in Odoo if the fiscal year calendar differs from the source, which we document as a post-load reconciliation step. Asset account and depreciation account codes from Exact Globe must map to Odoo account.asset.category field definitions before the asset import begins.

Exact Globe custom fields on any of the 14 supported standard tables (Financial entries, Accounts, Invoices, Items, Orders, Projects, HR, Contact persons) are cataloged during discovery and pre-created in Odoo as ir.model.fields before the corresponding data import. Field type mapping from Exact Globe types (text, long, double, date, bit) maps to Odoo field types (char, text, float, datetime, boolean). Custom field names are locked in Exact Globe after creation and must not change between discovery and load; we confirm final schema with the customer before extraction begins.