ERP migration
Field-level mapping, validation, and rollback between Access SupplyChain and Odoo ERP. We move data and schema; workflows are rebuilt natively in Odoo ERP.
Access SupplyChain
Source
Odoo ERP
Destination
Compatibility
10 of 12
objects map 1:1 between Access SupplyChain and Odoo ERP.
Complexity
BStandard
Timeline
5-8 weeks
Overview
Moving from Access SupplyChain to Odoo ERP is a supply-chain and ledger migration that requires careful sequencing of transactional data, explicit account structure mapping, and a documented extraction approach for each object type. Access SupplyChain does not publish a comprehensive public REST API, so we agree on an extraction method during discovery — database-level exports, supported reporting exports, or API calls where available — before any data movement begins. We handle Customers and Suppliers as Partner records, Purchase Orders as 1:1 PO documents, Items as Products with category and UoM preserved, and Warehouses as Locations with bin structure intact. Open AP and AR are migrated as vendor bills and customer invoices with a reconciliation worksheet for any payments in transit between export and go-live. Access Studio custom fields are enumerated individually and mapped to Odoo custom fields via ir.model.fields. We do not migrate workflows, automations, or Coins Evo construction-specific data as code — we deliver a written inventory for your admin to rebuild in Odoo Studio.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Access SupplyChain object lands in Odoo ERP, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Access SupplyChain
Customer
Odoo ERP
res.partner (customer type)
1:1Access SupplyChain Customer records (name, contact details, payment terms, credit limit) map to Odoo res.partner with partner_type set to customer. Address fields (street, city, postcode, country) map to partner address fields. Payment terms from Access map to Odoo property_payment_term_id. Customer category assignments from Access map to res.partner.category entries created during configuration.
Access SupplyChain
Supplier
Odoo ERP
res.partner (supplier type)
1:1Access SupplyChain Supplier records (address, bank details, category assignments) map to Odoo res.partner with partner_type set to supplier. Bank details (account name, sort code, account number) map to res.partner.bank_ids with appropriate bank fields. Supplier-to-customer relationship records in Access SupplyChain require explicit mapping to Odoo Contact records linked to the parent Partner if the same entity serves both roles.
Access SupplyChain
Purchase Order
Odoo ERP
purchase.order
1:1Open and historical purchase orders migrate to Odoo purchase.order records. Access SupplyChain status values (Draft, Sent, Received, Cancelled) map to Odoo's state field (draft, sent, purchase, cancel). PO line items map to purchase.order.line with Product2 reference resolved at migration time. Closed POs migrate as read-only records unless the destination requires open status for audit continuity.
Access SupplyChain
Item
Odoo ERP
product.product
1:1Item master records (SKU, description, unit of measure, cost price, sales price) map to Odoo product.product and product.template. Where items use variant attributes in Access SupplyChain, these map to Odoo product.attribute and product.attribute.value before variant generation. Deduplication is applied for merged or archived items flagged during discovery. Product categories from Access map to product.category entries created before import.
Access SupplyChain
Warehouse / Location
Odoo ERP
stock.location
1:1Warehouse records and bin locations migrate to Odoo stock.location with location_type set to internal (warehouse) or internal (stock location). Stock-on-hand is extracted as a cutover snapshot and applied as stock.quant records at go-live to avoid mid-migration discrepancies. Multi-warehouse setups require separate location trees per warehouse configured before item quantities are loaded.
Access SupplyChain
Chart of Accounts
Odoo ERP
account.account
lossyThe chart of accounts structure migrates to Odoo account.account entries. Access SupplyChain's per-entity account codes require pre-migration mapping because Odoo's multi-company accounting requires each company to have its own account records or share accounts via cross-company rules. We conduct an account structure interview during discovery and generate a mapping worksheet before any ledger data is loaded.
Access SupplyChain
Open AP
Odoo ERP
account.move (vendor bill)
1:1Outstanding vendor invoices and credit notes migrate as Odoo account.move records with move_type = 'in_invoice' or 'in_refund'. We flag payments in transit between export date and go-live date to prevent double-posting. Partial payments and allocations require a reconciliation worksheet as part of the cutover package. Vendor bill lines map to account.move.line with account_id resolved from the chart of accounts mapping.
Access SupplyChain
Open AR
Odoo ERP
account.move (customer invoice)
1:1Outstanding customer invoices and credit notes migrate as Odoo account.move records with move_type = 'out_invoice' or 'out_refund'. Customer payment allocations require the same reconciliation worksheet treatment as AP. Any payments received between export and go-live require manual re-application in Odoo after migration. Sales tax codes from Access map to Odoo account.tax records configured before invoice import.
Access SupplyChain
Document Attachments
Odoo ERP
ir.attachment
1:1Documents attached to suppliers, items, and purchase orders in Access SupplyChain are exported and linked to their destination Odoo records via ir.attachment. File size and format checks are performed during scoping; very large files or unsupported formats are flagged for customer review before migration. Attachment associations (which document belongs to which record) are preserved through record ID tracking during the export phase.
Access SupplyChain
Custom Fields (Access Studio)
Odoo ERP
ir.model.fields (manual)
lossyAccess Studio custom fields are enumerated during discovery using Access Studio's field registry. Each custom field is assessed for Odoo field type compatibility: character fields map to char, numeric fields to float or integer, date fields to date. Fields with unsupported data types (embedded objects, calculated aggregates) are flagged in the scoping document. Custom fields are created via ir.model.fields with state='manual' before main record migration begins.
Access SupplyChain
Users and Roles
Odoo ERP
res.users and res.groups
1:1Access SupplyChain user accounts map to Odoo res.users records. Role naming conventions differ between Access SupplyChain versions and Odoo, so role mapping is performed manually during scoping. Active users are migrated as active=True; inactive users are migrated as active=False with a note in the handoff document. Odoo access rights are assigned via res.groups membership based on the customer's role mapping worksheet.
Access SupplyChain
Stock Snapshot
Odoo ERP
stock.quant
1:1Stock-on-hand is extracted as a cutover snapshot from Access SupplyChain and loaded into Odoo stock.quant records at go-live, after warehouse locations are configured. This approach avoids the inventory discrepancies that arise when stock movements occur mid-migration between export and import. Any inventory transactions in Access SupplyChain during the migration window are documented for manual review or delta import.
| Access SupplyChain | Odoo ERP | Compatibility | |
|---|---|---|---|
| Customer | res.partner (customer type)1:1 | Fully supported | |
| Supplier | res.partner (supplier type)1:1 | Fully supported | |
| Purchase Order | purchase.order1:1 | Fully supported | |
| Item | product.product1:1 | Fully supported | |
| Warehouse / Location | stock.location1:1 | Fully supported | |
| Chart of Accounts | account.accountlossy | Mapping required | |
| Open AP | account.move (vendor bill)1:1 | Fully supported | |
| Open AR | account.move (customer invoice)1:1 | Fully supported | |
| Document Attachments | ir.attachment1:1 | Mapping required | |
| Custom Fields (Access Studio) | ir.model.fields (manual)lossy | Fully supported | |
| Users and Roles | res.users and res.groups1:1 | Mapping required | |
| Stock Snapshot | stock.quant1:1 | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Access SupplyChain gotchas
Sparse public API documentation complicates automated extraction
Multi-company and multi-segment account structures require pre-migration mapping
Open AP/AR reconciliation is not automatic at cutover
Odoo ERP gotchas
No rollback for CSV imports
External ID conflicts on re-import
Many2many field encoding in CSV imports
Large export timeouts require batching
Version schema drift between Odoo releases
Pair-specific challenges
Migration approach
Discovery and extraction method agreement
We audit the Access SupplyChain environment to identify active modules (supply chain, finance, Coins Evo if applicable), estimate record counts for each object type, and assess which extraction methods are available for each entity. We review any Access Studio custom fields, multi-entity account structures, and open AP/AR aging. The discovery output is a written migration scope document that specifies extraction methods per object, a preliminary object mapping, and an Odoo edition recommendation (Standard or Custom) based on multi-company requirements and custom field complexity.
Odoo environment setup and schema design
We configure the Odoo environment before any data arrives. This includes installing required apps (Purchase, Inventory, Accounting, Contacts), creating product categories and UoM classes, configuring chart of accounts using the account mapping worksheet, setting up warehouse locations and bin structures, and creating custom fields via ir.model.fields for any Access Studio extensions. Multi-company configuration is deployed if the scoping identified more than one legal entity. All schema work is performed in a staging Odoo database for validation before production migration begins.
Staging migration and reconciliation
We run a full migration into the staging Odoo environment using production-equivalent data volume. The customer reconciles record counts (Suppliers in, Customers in, POs in, Items in, open AP and AR in), spot-checks 25-50 random records against the Access SupplyChain source, and validates account code assignments. Any mapping corrections, missing UoM classes, or category gaps are resolved in staging before the production migration plan is finalised.
Owner and user provisioning
Access SupplyChain user accounts are mapped to Odoo res.users records by email match. Any Access user without a matching Odoo user account is held in a provisioning queue for the customer's Odoo admin to create before record migration resumes. Role assignments from Access SupplyChain are mapped to Odoo group memberships using the role mapping worksheet. This step must complete before transactional record migration begins because OwnerId references on Purchase Orders and Partner records require resolved user references.
Production migration in dependency order
We run production migration in record-dependency order: UoM classes and product categories first, then Warehouses and Locations, then Partners (Customers and Suppliers), then Products, then Purchase Orders, then open AP and AR (vendor bills and customer invoices), then Attachments, then Custom Fields data, then stock quant snapshot at go-live. Each phase emits a row-count reconciliation report before the next phase begins. The sparse API documentation means extraction for certain object types may be file-based rather than API-based; we document this transparently in the migration runbook.
Cutover, validation, and handoff
We freeze Access SupplyChain writes during cutover, run a final delta import for any records modified during the migration window, then enable Odoo as the system of record. We deliver the open AP/AR reconciliation worksheet, a custom field mapping summary, and a document noting any Access Studio fields that could not be migrated as typed fields (with recommended Odoo Studio equivalents). We support a one-week hypercare window for reconciliation issues. We do not rebuild Access SupplyChain workflows, automations, or Coins Evo construction-specific data as code; we deliver a written inventory for the customer's admin to configure in Odoo Studio or with a construction-specific Odoo app.
Platform deep dives
Access SupplyChain
Source
Strengths
Weaknesses
Odoo ERP
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Access SupplyChain and Odoo ERP.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Access SupplyChain: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Access SupplyChain doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Access SupplyChain to Odoo ERP migration scoping. Not seeing yours? Book a call.
Walk through your Access SupplyChain to Odoo ERP migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Access SupplyChain
Other ways to arrive at Odoo ERP
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.