Migrate from Base ERP to Odoo ERP

Base ERP Warehouses map directly to Odoo Warehouse records. Each Base ERP warehouse name becomes the Odoo warehouse name and code (short code derived from first three letters). We also map the warehouse's address fields to Odoo's partner address on the warehouse record. Multiple warehouses in Base ERP each create separate stock.warehouse records with their own location hierarchies under stock.location (view type) down to stock.location (partner locations type).

Base ERP Offers (products) map to Odoo product.template for the shared product record and product.product for individual variants. The Base ERP SKU (hs_sku equivalent or listing ID) becomes the Odoo product.default_code. We handle variant logic: if Base ERP stores variant attributes (size, color) as separate columns, we create product.attribute and product.attribute.value records in Odoo and generate variant combinations. The product description, images, and dimensions migrate as extra fields on product.template. Large catalogs over 5,000 SKUs are chunked into batches of 500 to stay within Odoo import batch limits.

Base ERP stock quantities per warehouse per product map to Odoo stock.quant records. The quant captures product_id, location_id (the specific warehouse sub-location), quantity, and lot_id if applicable. We capture a point-in-time snapshot at migration start to avoid inconsistencies from live inventory syncs during the transfer window. lot_id and lot_number fields are populated if Base ERP tracks serial or lot numbers; otherwise, quant records use the warehouse root location with lot tracking disabled.

Base ERP pricing rules defined per marketplace channel, per quantity tier, or via rule sets map to Odoo product.pricelist records (one per channel or pricing strategy) with product.pricelist.item child records. Base ERP's flat key-value pricing export expands into Odoo's rule-based price computation: fixed_price, percent_price, or formula-based computation stored in the item's compute_price field. We preserve the original currency assumption (typically PLN for Allegro-heavy accounts or EUR for cross-border) and set the Odoo pricelist currency accordingly.

Base ERP Orders map to Odoo sale.order records with line items on sale.order.line. We map customer name and address to the Odoo partner record (created from the order's customer details if no matching partner exists), order status to Odoo order state (sale_order_state), and payment method to a custom field on the order. Historical orders include fulfillment tracking information mapped to Odoo's stock.picking records and delivery address fields. We export open and completed orders; completed orders preserve their original creation date via date_order.

Base ERP customer records (embedded in orders if not stored as standalone Company records) map to Odoo res.partner. We distinguish between customer-type partners (customer = True) and supplier-type partners (supplier = True). Base ERP's company name maps to partner name, email to partner email, phone to partner phone, and address fields to partner street, city, and country. Duplicate customers are merged by email match before import to avoid creating multiple res.partner records for the same buyer.

Base ERP marketplace connector configurations (channel type, listing IDs, sync rules for eBay, Amazon, Allegro) are not directly migratable because API credentials and tokens cannot be extracted from BaseLinker. We export the connector mapping table (channel, listing_id, offer_id, sync_direction, and any active rules) as a structured document that the customer's Odoo administrator or Odoo partner uses to reconfigure each channel connector in Odoo. No credentials are transferred; manual re-entry is required per platform's OAuth or API key flow.

Base ERP user accounts (Admin, Operator, Warehouse Manager roles) map to Odoo res.users. We extract the user's name and email as the Odoo login. Role assignments from Base ERP are preserved as a custom field note (base_erp_role__c) on the res.users record if Odoo's standard groups do not map cleanly. Any Base ERP user without a corresponding Odoo user is placed in a reconciliation queue for the customer's admin to provision before record import resumes.

Base ERP custom product fields (e.g., custom dimensions, certifications, seasonal flags) stored as extra CSV columns map to Odoo product.template custom fields. We create ir.model.fields entries for each custom field with the appropriate Odoo field type (char, float, integer, boolean, selection, or text). These fields appear on the product template form view after the migration. Type casting is applied during the transform step: numeric strings become float or integer fields, boolean-like values ('yes'/'no', 'true'/'false') become boolean fields.

Invoice generation is not a core Base ERP module; it is typically handled by an external accounting tool integrated via BaseLinker. We do not migrate invoice records as part of standard scope. Customers should export invoices directly from the connected accounting tool and import them into Odoo Accounting separately. The Odoo Accounting app maintains its own journal entries and move records that are not derived from Base ERP data.