Migrate from EZ Office to Odoo CRM

EZ Office vendors map to Odoo res.partner records with the supplier flag set to True. Company-type partners use partner_type='company'; individual vendors use partner_type='person'. Vendor-specific fields such as tax ID and payment terms from EZ Office migrate to custom fields on res.partner (x_vendor_payment_terms, x_vendor_rating). The email field on res.partner enables later linking to purchase orders via Odoo's purchase module.

EZ Office members map to Odoo res.partner records with the customer flag set to True. Members with company associations link to a parent res.partner record for the company using parent_id. Member-specific properties such as membership tier and join date migrate as custom fields (x_membership_type, x_ezo_join_date) on res.partner. The customer_rank field is set to 1 to enable proper customer portal access in Odoo.

EZ Office assets split across two Odoo objects: product.product for the asset template (name, category, default_code) and stock.quant for the inventory instance tracking location_id, quantity, lot/serial number. Consumable vs. storable classification in EZ Office drives the product type in Odoo (product.type field). Serial numbers on assets create stock.production.lot records linked via lot_id on the quant.

EZ Office Asset Stock records map directly to Odoo stock.quant entries. The location_id in Odoo corresponds to the EZ Office location hierarchy, preserving the storage context for each item. Quantity on hand translates directly to the quant's quantity field. Lot/serial numbers from EZ Office map to stock.production.lot records, which then link to the appropriate quant via lot_id.

EZ Office locations migrate to Odoo stock.location records preserving the complete hierarchical structure. The full hierarchical path from EZ Office (available via the 'Show hierarchical location in item listings' company setting) maps to Odoo's parent_path field, which stores the ancestry chain for tree queries and filtering. Each location also receives its location_type designation (internal, inventory, production) matching EZ Office's location classification.

EZ Office users map to Odoo res.users by email match using the login field. Admin-level users in EZ Office may become Odoo group 'Sales / Administrator' or 'Inventory / Manager' based on their role flags and access levels. Standard users map to 'Sales / User' or 'Stock / User' groups. Unmatched users are flagged before migration for manual Odoo user creation.

EZ Office groups (departments or teams managing assets) map to Odoo crm.team records preserving the team structure. Team member assignment in EZ Office maps to crm.team member_user_ids in Odoo, linking the migrated res.users to their respective sales teams. Each team receives its own pipeline with stage configuration in Odoo CRM, with stages created during the pre-migration schema setup phase.

EZ Office documents linked to assets or members migrate as Odoo ir.attachment records with res_model and res_id pointing to the migrated product.product or res.partner record respectively. Binary file content is downloaded from EZ Office via the per-record export mechanism and pushed to Odoo's filestore through the ir.attachment datas field using base64 encoding.

EZ Office canned reports contain data summaries that have no direct Odoo equivalent. We export the report data as CSV and attach it as an ir.attachment to the relevant Odoo record for reference. The reporting logic must be rebuilt in Odoo's pivot views and custom dashboards.

EZ Office inventory items map to Odoo product.product records maintaining item-level detail. Item categories in EZ Office map to product.category in Odoo preserving the categorization hierarchy. Quantity fields including on-hand, committed, and forecast quantities translate to stock.quant entries for current inventory positions and product-template virtual_available fields for planning visibility.

EZ Office custom fields on any object require Odoo custom field creation using the x_ prefix on the target model before migration begins. We generate the field creation plan as part of the pre-migration schema setup. Field type mapping follows these translations: text fields map to char, numbers map to float, dates map to date, and dropdown selections map to selection fields in Odoo.