Migrate from Clear Enterprise to Odoo ERP

Clear Enterprise Projects map to Odoo Project. We discover the full project schema during profiling — stage, deadline, priority, budget, and custom fields are all mapped individually. The parent-team relationship from Clear Enterprise maps to Odoo's Project Team or Analytical Account depending on the Odoo edition in use. Projects must be imported before Tasks because Tasks carry a project_id foreign key.

Clear Enterprise Tasks map to Odoo Project Task. We preserve the parent_project_id reference by sequencing Project import first. Any custom task fields (priority tiers, billable flags, skill tags) migrate to Odoo custom fields via Odoo Studio or direct Python field definition in the destination database. Task state mapping requires a manual review of the source stage labels against Odoo's kanban stage values.

Every Clear Enterprise deployment carries a different set of custom object types. During schema profiling we discover all named object types and their field definitions. Each custom object maps to an Odoo custom model created via Odoo Studio or direct ORM in the destination. Lookup relationships between custom objects and standard objects (Projects, Contacts) are pre-created as Many2one or Many2many fields before data import. Edition constraints: Odoo Community supports custom models via Python development; Odoo Studio provides a GUI in Enterprise.

Clear Enterprise Contacts map directly to Odoo Contact (res.partner with type=contact). Name, email, phone, street address, city, country, and website migrate as standard fields. The owner assignment (assigned user in Clear Enterprise) maps to Odoo's user_id field by email resolution. Address fields are mapped to Odoo's street, street2, city, state_id, zip, country_id structure.

Clear Enterprise Companies map to Odoo Company (res.partner with type=company). The company_id reference on Contact records is preserved by importing Companies first. Company-specific custom fields (industry classification, VAT number, annual revenue) map to custom fields on the res.partner record. Odoo's multi-company model requires a parent_company_id assignment if the destination uses multiple Odoo companies.

Clear Enterprise Documents attach to Projects, Tasks, and Custom Objects. We export each file individually and re-associate it to the correct parent record in Odoo using the res_model and res_id fields on ir.attachment. File names, MIME types, and binary content are preserved. Large binary attachments (>5 MB) are chunked during upload to respect Odoo's attachment size limits. If Clear Enterprise stores document metadata (version, author, tags), we map these to custom fields on ir.attachment or to tags via Odoo's document module if the Enterprise edition is in use.

Clear Enterprise Users map to Odoo res.users by email match. Role and permission translation requires a per-implementation review because Clear Enterprise role definitions are custom per deployment. We map Clear Enterprise roles to Odoo's access rights groups (Project User, Project Manager, Officer, Employee) during scoping and document any roles with no direct Odoo equivalent for the customer admin to configure post-migration.

Clear Enterprise Teams aggregate Users and control access scoping. Where the destination uses Odoo's flat permission model (res.groups), we flatten team hierarchies accordingly. Teams with nested sub-teams are resolved to a single group membership per user. If Odoo Enterprise is in use, we can map Teams to Odoo Discuss channels for collaboration purposes, though this is a functional rebuild rather than a data migration.

Clear Enterprise GL transaction data requires careful Chart of Accounts mapping. We profile the source account codes, account names, and account types (Asset, Liability, Equity, Revenue, Expense) and map each to an Odoo account.account record with the correct account_type and code fields. Currency alignment (CHF source, multi-currency Odoo destination) is validated against Odoo's multi-currency configuration. Effective-dated balances migrate as opening balance entries on the account.account records.

Historical GL transactions from Clear Enterprise map to Odoo account.move records (account.move with type=entry). Each transaction line maps to account.move.line with the corresponding account_id, debit, credit, and analytic_account_id references. Journal ID is resolved from the mapped Chart of Accounts journal assignment. Tax codes on source transactions map to Odoo account.tax records. Lock dates are set in Odoo to prevent posting to closed fiscal periods.