Migrate from Everwin to Odoo ERP

Everwin Customer records map to Odoo res.partner with partner_type set to 'contact' for individuals and 'company' for organizations. The Everwin customer code becomes the Odoo partner's ref field. Address fields (street, city, zip, country) migrate directly. We apply country-specific VAT validation and create a fiscal_position rule if the Everwin customer has a VAT number mapped to a jurisdiction different from the company's country.

Everwin organizational Customers map to Odoo res.partner with is_company=True, and related contact persons become child res.partner records attached via parent_id. We use the Everwin customer_name as the Odoo company name and extract domain from any email field to populate the Website field on the company record.

Everwin Vendor records map to Odoo res.partner with supplier_rank set to 1 or higher, indicating a supplier relationship. Payment terms, bank details (acc_number, bank_id), and the vendor's default credit limit migrate to Odoo partner fields. If Everwin stores a supplier code, it maps to the Odoo partner ref field for purchasing document matching.

Everwin invoice and AP/AR transaction records map to Odoo account.move. Open invoices migrate as account.move with state='draft'; paid invoices migrate with state='posted' and matched payment records (account.payment) if Everwin payment records are available. Everwin's invoice number becomes Odoo's name sequence. Journal_id is resolved based on invoice type: sale journal for customer invoices, purchase journal for vendor bills.

Everwin account codes and names are exported in full, then mapped against Odoo's French or Belgian CoA template (depending on the customer's jurisdiction) during a reconciliation session. We present a three-column matrix: Everwin account code, Everwin account name, Odoo account suggestion (with account.type and deprecated flag). The customer approves the mapping before any account.move records are loaded. Custom Everwin accounts without a template equivalent are created as Odoo custom accounts with a customer-approved type.

Everwin tax codes tied to jurisdiction (TVA in France, BTW in Belgium) map to Odoo account.tax records. We export the Everwin tax code set, match each to the Odoo country-specific tax template (e.g., tva_21_default, tva_10_reduced), and present a mapping table for the customer to validate. Any Everwin tax code without an Odoo template equivalent is created as a custom account.tax with the correct amount, tax_group, and invoice_repartition_line configuration.

Everwin Project records map to Odoo project.project. Custom fields on the Everwin Project object are introspected during scoping, then created as custom.char, custom.selection, or custom.float fields on the Odoo project.project model. Project status (status_workflow field) maps to Odoo's kanban_state (normal, blocked, done). If Everwin uses project hierarchies or parent projects, we create project.task hierarchy in Odoo to preserve the structure.

Everwin document attachments are exported as binary blobs with parent entity reference and filename. We map the parent Everwin entity type to the Odoo model (res.partner, account.move, project.project) and the Everwin entity ID to the Odoo res_id. The ir.attachment record is created with name=filename, res_model=mapped_Odoo_model, res_id=target_record_id, and the binary stored in the Odoo ir_attachment table or file store depending on the Odoo edition's storage configuration. Binary format and storage location vary by Everwin installation and are validated during scoping.

Everwin Item records (SKU, description, unit_cost, custom attributes) map to Odoo product.template. The Everwin item code becomes product.default_code (the SKU field). Unit cost from Everwin maps to standard_price on product.template. We create product.category entries based on any Everwin category or product family field. Custom attributes on Everwin Item are introspected and created as product.attribute and product.template.attribute.value records in Odoo if the customer requires variant tracking.

Everwin User records with roles and permissions map to Odoo res.users. We export User email, name, and role assignment. In Odoo, we map Everwin roles to Odoo access groups (res.groups): Everwin admin role maps to Odoo Settings / Technical / Access Rights; Everwin sales role maps to Sales / User; Everwin accountant role maps to Accounting / Accountant. The customer provisions Odoo users before migration (active or inactive status based on the Everwin user's active status). Email is used as the Odoo login.

Everwin custom objects are unique per installation. We introspect the v3 API schema for each custom object during scoping, capture field names, data types, and relationships, then create corresponding Odoo model definitions (ir.model) with matching fields (ir.model.fields) before migration begins. Any lookup relationships in the Everwin custom object (foreign key references to Customer, Project, or other entities) are resolved as Odoo many2one fields pointing to the mapped target model. The customer approves the Odoo custom model design before any records are loaded.