Migrate from PILOT:Suite to Odoo ERP

PILOT:Suite Item records map to Odoo product.product (stockable or consumable depending on stock tracking configuration). Item attributes and custom module fields become Odoo product attributes, product variants, or custom fields via Odoo Studio. The PILOT:Suite SKU maps to product.default_code, and the item description maps to product.description. If PILOT:Suite Items have multiple warehouse assignments, each assignment becomes an Odoo quant record in the corresponding stock.location after the warehouse locations are created.

PILOT:Suite Warehouse records map to Odoo stock.warehouse. Each warehouse gets a matching name, code, and address. The warehouse's locations (shelves, bins) map to Odoo stock.location records under the warehouse's view location. Removal strategies (FIFO, LIFO, FEFO) from PILOT:Suite transfer to Odoo's route configuration on the warehouse.

PILOT:Suite Vendor records map to Odoo res.partner with the Vendor category applied. Vendor-specific fields (tax ID, payment terms, lead times) map to the partner's fields or to Odoo Purchase app fields (product.supplierinfo for vendor-specific pricing and lead times). If PILOT:Suite vendors also appear as customers, the same res.partner record gets both Vendor and Customer categories.

PILOT:Suite Customer records map to Odoo res.partner with the Customer category applied. Customer-specific fields (credit limit, payment terms, invoice and delivery addresses) map to the partner's address fields, sale_partner_id, and property fields. Customer-specific pricing tiers from PILOT:Suite become Odoo product.pricelist records applied to the customer.

PILOT:Suite Purchase Orders map to Odoo purchase.order. Open POs in draft or confirmed state migrate as draft purchase orders. Line items (PO lines) map to purchase.order.line with product, quantity, price, taxes, and delivery date. PILOT:Suite PO status (pending, partially received, closed) maps to Odoo PO state with the corresponding receipt quantities represented as existing stock moves or moves to be created. Closed/cancelled POs do not migrate as active orders but their totals contribute to historical reporting totals.

PILOT:Suite Sales Orders map to Odoo sale.order. Open SOs in draft, confirmed, or in-delivery states migrate as corresponding Odoo sale.order states. Line items migrate as sale.order.line with product, quantity, price, taxes, and scheduled date. PILOT:Suite order status determines Odoo state. Fulfilled SOs are migrated as locked or closed orders for historical reporting; cancelled SOs are not migrated as active orders.

PILOT:Suite GL Accounts map to Odoo account.account with account type mapping based on account use: asset accounts to receivable/payable or non-current asset types, liability accounts to payable or credit card types, equity accounts to equity type, income accounts to revenue type, expense accounts to expense type. PILOT:Suite account balances are extracted at the migration cutoff date and set as Odoo opening balance entries (account.move with type=opening_revaluation) rather than being re-entered through standard journal entries.

PILOT:Suite open AP (money owed to vendors) and open AR (money owed by customers) map to Odoo account.move records of type in_invoice (vendor bills) and out_invoice (customer invoices). Each open PILOT:Suite AP/AR item becomes a draft Odoo invoice with the vendor/customer partner, invoice lines, due date, and amount. Payment state is set to not_paid pending reconciliation after payment in Odoo. Historical paid invoices from PILOT:Suite are migrated as locked account.move records with payment reconciled.

PILOT:Suite custom fields configured in the system's module structure are mapped to Odoo custom fields via Odoo Studio (for standard object customizations) or custom Python fields on the relevant model. PILOT:Suite field types are matched to Odoo field types: char/text to char/text, number to float/monetary, date to date, dropdown to selection. PILOT:Suite custom modules that represent industry-specific entities (e.g., lot tracking, EDI partner configuration) are documented and delivered as a separate configuration guide for Odoo implementation.

PILOT:Suite chart of accounts with extracted balances at migration cutoff are loaded into Odoo as opening journal entries using the opening_revaluation move type. Each PILOT:Suite GL Account with a balance becomes one or more debit/credit lines in the Odoo opening entry, with the account.move reconciled against the opening balance account configured in Odoo's accounting settings. We flag any PILOT:Suite accounts that do not have a clear Odoo account type equivalent for the customer's accountant to resolve before import.

PILOT:Suite item-to-warehouse assignments determine initial Odoo stock.quant records. For each Item-Warehouse pair with on-hand quantity, we create a stock.quant record at the appropriate warehouse location. If PILOT:Suite uses location-based lot or serial tracking, those become Odoo stock.production lots with the corresponding lot number and expiration date. Routes and replenishment rules are configured as Odoo stock.rule records after the initial quant import.