Migrate from Scopevisio to Odoo ERP

Scopevisio's Organisation and Branch hierarchy maps to Odoo's Company records. Each Scopevisio Organisation is a separate legal entity with its own chart of accounts, customer ledger, and vendor ledger. We treat each Organisation as an independent export scope and create a corresponding Odoo Company record before any related data imports, preserving the Organisation's name, address, tax ID, and currency settings. Branches that are cost-centre only (no separate legal entity) map to Odoo analytic accounts or sections within the parent Company.

Scopevisio Customer master records (with individual and company subtypes) map to Odoo Contact records with the Customer checkbox enabled. The customer number, name, address, email, phone, and classification fields migrate directly. Scopevisio's customer-specific payment terms and price lists map to Odoo Property fields (property_payment_term_id, property_product_pricelist). Individual-type customers and company-type customers both map to Contact; Odoo distinguishes them via the Company Type field.

Scopevisio Vendor master records map to Odoo Contact records with the Vendor checkbox enabled. Vendor-specific fields (bank details, payment terms, vendor-specific notes) migrate to Odoo's res.partner fields and property fields. Banking details from Scopevisio (IBAN, BIC) map to Odoo's partner bank account model (res.partner.bank). We flag any vendor record that also exists as a customer in Scopevisio for dual-flag mapping in Odoo.

Scopevisio's hierarchical chart of accounts with German SKR types (SKR03, SKR04) and tax codes maps to Odoo's account.account records. We extract the full account structure including account type (asset, liability, equity, income, expense), account code, and account name. German tax codes (Vorsteuer, Umsatzsteuer, Reverse Charge) are mapped to Odoo tax groups and account tags. Any Scopevisio custom account types that have no direct Odoo equivalent are flagged for manual configuration review before the accounting migration phase begins.

Scopevisio outgoing and incoming invoices and credit notes map to Odoo Account Move records. Invoice header fields (number, date, due date, currency, tax totals) migrate directly. Line items map to Account Move Lines with account_id resolved to the mapped Odoo account, product_id resolved where applicable, and tax_ids resolved to Odoo tax records. Invoice status (open, paid, cancelled) migrates as move state. Scopevisio's separate invoice document and invoice status fields are both preserved in custom fields on the Odoo account move for audit continuity.

Scopevisio Projects map to Odoo Project records, including project hierarchy, billing method (time and material, fixed price, non-billable), and associated cost centres. Project stage statuses are mapped to Odoo stage values, and any custom project fields from Scopevisio migrate to Odoo custom fields on project. We preserve the project code and associate each project with its Odoo Company (from the Scopevisio Organisation mapping) and analytic account.

Scopevisio time entries map to Odoo Timesheet entries (account.analytic.line) associated with the relevant project, employee, and billing record. Entry date, hours, description, and billing status migrate directly. If Odoo's Timesheet app is not licensed, time entries map to Odoo Meeting or Task records with custom hour fields instead, chosen during scoping based on the customer's Odoo plan.

Scopevisio DMS/ECM documents are exported from GDPdU archives or direct file export and re-associated to Odoo records via IrAttachment. We unpack GDPdU archives to separate structured accounting data from embedded document files, identify each document's parent object (customer, vendor, invoice, project), and attach the file to the corresponding Odoo record. Odoo's Document app (if licensed on Custom plan) creates a structured folder hierarchy matching Scopevisio's document organisation. Files are re-uploaded in their original format with filename and attachment metadata preserved.

Scopevisio employee master records (name, department, role, organisational hierarchy) map to Odoo Employee records. Effective-dated compensation, PTO balances, and payroll records map to Odoo Payroll (if the Payroll app is licensed on the destination Odoo Custom plan) or are preserved in a structured CSV export for the customer's payroll administrator to re-enter. Scopevisio's multi-company employee assignments are resolved by mapping each employee to an Odoo Employee record under the corresponding Company.

Scopevisio Items with pricing, unit of measure, and stock-control flags map to Odoo Product Template records. Item codes migrate as Product barcodes or product code fields. We flag any Scopevisio items with Bill of Materials (BOM) structures or multi-level kits for Odoo manufacturing app configuration review. Stock-control flags map to the Odoo product's can_be_expensed, sale_ok, and purchase_ok boolean fields. Custom pricing tiers on Scopevisio items map to Odoo pricelist rules.

Scopevisio Fixed Asset records (acquisition cost, depreciation method, asset classification, location) map to Odoo Asset records if the Odoo Accounting app is licensed. Depreciation method and schedule are preserved. Some Odoo editions handle asset depreciation through the accounting module rather than a dedicated asset management app; we configure this distinction during scoping based on the customer's Odoo plan. Asset value history and depreciation journals are mapped to Odoo's asset journal entries.

Scopevisio customisable fields on standard objects (customer, vendor, project, invoice) are discovered during scoping and mapped to Odoo custom fields (ir.model.fields with attribute translate=True for localised text fields). We handle type differences: Scopevisio date, text, and picklist fields map to their Odoo equivalents (date, char/text, selection). Any custom object types in Scopevisio map to Odoo custom models (ir.model) created during the schema design phase before data import begins.