Migrate from Sage 200cloud to Odoo ERP

Sage 200cloud Nominal Accounts map to Odoo Account records within the configured chart of accounts. We export via the Nominal Account CSV report, map the account code, name, and nominal_type (balance sheet vs profit and loss), and import in the required Sage sequence — after Departments and Cost Centres are pre-loaded as Account Groups in Odoo. Sage's active/inactive status maps to Odoo's active flag. We flag any Sage nominal accounts with a Department or Cost Centre reference and map those to Odoo Analytic Account tags for dimensional reporting.

Sage 200cloud enforces that Nominal Accounts cannot reference non-existent Departments or Cost Centres during import. We pre-load both as Odoo Analytic Accounts (used for dimension tagging on journal lines) and as Account Groups (used for financial statement sectioning) before any Nominal Account import. The mapping preserves the Department and Cost Centre hierarchy so that Odoo's Analytic Reporting can replicate the cost-centre breakdown in the destination.

Sage 200cloud Customer records map to Odoo Contact with the company flag set to true. We export via the Customer Record CSV report, mapping account_ref to Odoo's ref field, customer_name to name, payment_terms to property_payment_term_id, and the nominal code assignment to the accounts receivable field. We detect and flag email fields exceeding Sage's Known Issue 8225 limit of 215 characters, then truncate or flag records for manual correction before destination import.

Supplier records follow the same CSV export mechanism as Customers. We map Supplier payment terms, bank details, and nominal code assignments to Odoo's vendor contact properties (property_supplier_payment_term_id, bank_ids). The supplier_account flag is set to true on import so that the Contact appears in Odoo's vendor context for Purchase Order creation.

Sage 200cloud SOP documents — order headers, line items, and allocation quantities — are exported via the Sage reporting engine. We sequence SOP imports after Customer records and validate warehouse references against the Odoo stock locations. Order statuses (Confirmed, Despatched, Delivered) map to corresponding Odoo Sale Order state transitions. Any SOP lines referencing discontinued Stock Items are flagged for product remapping before import.

POP records are handled in the same dependency order as SOP: Suppliers are imported first, then Purchase Orders with warehouse validation. We preserve the Confirm Goods Received status and flag any records affected by Known Issue 8159 (extra blank columns in the POP form) during data extraction to avoid malformed rows in the destination.

Sage 200cloud Stock Items require strict import sequencing: Product Groups → Stock Items → Opening Balances → Supplier Price Lists. We export the full hierarchy and reconstruct it in Odoo as Product Categories (from Product Groups), Product Templates (from Stock Items with type set to product or consumable), and Product Variants if the source has size or colour variants. Opening balances map to Odoo Inventory Quantities against warehouse-specific locations. Supplier Price Lists map to Odoo Supplier Info records on the Product Template.

Sage 200cloud bank accounts are stored as Nominal records with specific type flags. We export via the nominal account CSV filtered by bank account type, then re-import as Odoo Bank and Cash Journals linked to the corresponding Account records. Opening balances and currency codes transfer faithfully, and we create matching Journal entries in the Odoo accounting app to establish the bank ledger opening position.

Fixed Assets in Sage 200cloud are tied to Nominal Accounts and carry acquisition date, depreciation method, and net book value. These require value-mapping for depreciation schedules because Odoo's Asset Management app uses a different depreciation computation engine. We map the acquisition value, acquisition date, depreciation method (straight-line, reducing balance, sum-of-years-digits), and asset category to Odoo's Asset and Asset Category records, flagging any records with non-standard depreciation methods for manual configuration review before import.

Posted invoices and credit notes are historical transaction records exported via the Sage reporting engine. Document references must match exactly between Sage and Odoo or Odoo will create duplicate entries. We preserve the full invoice header, line items, and tax codes, and map Sage invoice types (SOP Invoice, SOP Credit Note, POP Invoice, POP Credit Note) to the corresponding Odoo move_type values (out_invoice, out_refund, in_invoice, in_refund). Historical paid and unpaid status is preserved as Odoo move state.

Nominal budget records export alongside nominal transactions in Sage 200cloud. We chunk budget rows into the same import batch as the nominal chart-of-accounts data, maintaining period-level granularity. Odoo's Budget module (part of Analytic Accounting) requires budget items to be tagged with Analytic Accounts; we use the Department and Cost Centre mapping to resolve the Analytic Account reference on each budget line.

User-seat assignments in Sage 200cloud are tied to licensing tiers. We extract user records and map them to Odoo User accounts resolved by email match. Any assigned-ownership records in Sage (SOP assigned to a user, POP assigned to a user) that reference users not present in the destination are held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Sage users map to Odoo Portal users if the customer requires external customer or supplier portal access.