QUICK LINKS
Accounting
Bay Forward © 2026 - All Right Reserved
- casestudy
Passages International: NetSuite to Odoo Migration
Intro: Passages International: NetSuite to Odoo Migration
Founded in 1999 and headquartered in Albuquerque, New Mexico, Passages International is a leading supplier of biodegradable, eco‑friendly funeral products, including urns, caskets, scattering tubes, water‑burial urns, and memorial keepsakes, all designed with sustainability at their core.
As demand for green funerals has surged and cremation rates in the U.S. have climbed past 60% with projections above 80% by 2045, Passages has grown into a mission‑driven wholesale business serving funeral homes, distributors, and families across multiple continents. That growth created the need for an ERP platform that could scale with the business without the restrictive licensing, rigid architecture, and rising costs of their legacy system.
Passages International, Inc. undertook one of the highest‑stakes moves a finance team can make: migrating years of core financial history from NetSuite to Odoo without losing detail, continuity, or trust in the numbers.
Client Snapshot
Company
Passages International
Industry
Eco‑friendly wholesale & consumer products
Headquarters
Albuquerque, New Mexico, USA
Primary markets
North America and international distributors
Previous ERP
NetSuite
New Platform
Odoo (Enterprise)
Migration scope
Full financial data, reporting, training
Partner
Bayforward
Key challenges:
Passages faced a classic migration dilemma: how to move off NetSuite without breaking their financial continuity.
- Protecting the full financial story
NetSuite held years of detailed history — journal entries, invoices, bills, payments, and adjustments. Passages needed that history preserved in Odoo for audits, management reporting, and decision‑making, not just high‑level opening balances. - Complex differences between platforms
NetSuite and Odoo differ deeply in chart of accounts design, journal structure, period management, tax configuration, and reporting concepts. A naïve “export/import” would risk silent errors: data that appears loaded but no longer ties out. - Cost and agility constraints in NetSuite
NetSuite’s per‑user and per‑module pricing, coupled with the dependency on certified partners for customizations, made it harder for Passages to adapt the system quickly and cost‑effectively as the business evolved. - Change management for the finance team
The finance and operations teams were fluent in NetSuite. Simply dropping them into Odoo without context would have slowed adoption, increased errors, and undermined confidence in the new platform.
Phase 1
Discovery & Architecture Mapping
- ●Analyzed NetSuite chart of accounts, journal types, posting logic, AR/AP aging, sub-ledgers, and historical periods.
- ●Reviewed custom fields, classifications, and reporting dimensions to decide what to preserve or redesign.
- ●Designed an Odoo accounting model that kept Passages' logic while using analytic accounting and native reporting.
Phase 2
Full Historical Financial Data Migration
- ●Migrated full general ledger history — not just opening balances.
- ●Brought over invoices, credit memos, vendor bills, credits, payments, adjustments, and other journals.
- ●Enabled comparative reporting, historical drill-downs, and audits directly in Odoo.
Phase 3
Reconciliation & Completeness Validation
- ●Reconciled trial balances by period between NetSuite and Odoo.
- ●Matched AR/AP sub-ledgers and key balance sheet and P&L lines across periods.
- ●Resolved every discrepancy so Odoo balances matched NetSuite to the penny at go-live.
Phase 4
Reporting Architecture — Rebuilt, Not Copied
- ●Rebuilt financial statements with Odoo's financial report builder.
- ●Created management views using pivots and dashboards tailored to Passages' needs.
- ●Set up analytic accounting for deeper margin, customer, and product analysis.
Phase 5
Training & Platform Enablement
- ●Trained users by showing NetSuite tasks and their Odoo equivalents side by side.
- ●Explained differences in posting, reconciliation, and period close processes.
- ●Built confidence with Odoo's UI, filters, and reports so finance could run independently from day one.
Why move from NetSuite to Odoo?
Bayforward did not position this as “NetSuite bad, Odoo good.” Instead, we helped Passages evaluate fit for their size, growth plans, and operating model.
NetSuite pain points for Passages
- Escalating per‑user and per‑module subscription fees
- Customizations that required specialized partners and higher budgets
- A reporting architecture optimized for enterprise complexity, not mid‑market agility
- Limited flexibility in deployment and vendor lock‑in
What Odoo offered
- More predictable, usage‑based pricing without hidden module uplifts
- Open, flexible architecture that supports deep customization at lower cost
- Modern, intuitive UI that shortened the learning curve for non‑technical users
- Strong built‑in financial features, including analytic accounting and native dashboards
For Passages, the question wasn’t “Can we live without NetSuite?” It was, “Can we get the same financial clarity or better on a platform that aligns with our cost, agility, and control requirements?” Odoo, implemented by a team fluent in both systems, made that possible.
Key Implementation Highlights
Underestimating ERP migrations is common. Financial data isn’t just rows in a spreadsheet; it’s shaped by each platform’s logic.
- General Ledger & Chart of Accounts Alignment
NetSuite and Odoo use different GL structures and chart‑of‑accounts schemas, so each account had to be mapped or redesigned to preserve balances, classifications, and reporting groupings accurately after migration.
- Journal Structure & Period Control
Journal entry formats, posting rules, and period‑locking mechanisms differ between the two platforms, requiring careful treatment of historical entries, adjustments, and closed periods to maintain audit trails and prevent back‑posting.
- Sub‑ledger & Entity Architecture
AR/AP sub‑ledger relationships, customer/vendor linkages, and entity structures (NetSuite subsidiaries vs. Odoo multi‑company) are modeled differently, so open items, aging, and inter‑entity balances had to be re‑established in a way that still reconciled.
- Reporting, Analytics & Dimensions
NetSuite’s saved searches and SuiteAnalytics do not map directly to Odoo’s pivot views, analytic accounts, and native financial report builder, making it necessary to re‑engineer reports and dimensional analysis rather than simply replicate existing layouts.
- Tax Configuration, Custom Fields & Historical Treatment
Tax engines, compliance setups, and custom fields often lack one‑to‑one equivalents, and historical periods/opening balances are handled differently in each system; without deliberate design, these gaps can produce books that look complete but fail to reconcile in practice.
Client’s Testimonial
Result & Impact
Passages International’s migration from NetSuite to Odoo was not just successful. It was clean and confident‑building.
KEY INSIGHTS
Results & Impact
100%
historical financial data migrated into Odoo
Zero
reconciliation discrepancies at go‑live
2
ERP platforms mastered by the Bay Forward team
The business retained its full financial memory while gaining a more flexible, cost‑effective ERP foundation for the future. Instead of simply “moving off NetSuite,” Passages moved toward an environment where their data, reporting, and team capabilities are better aligned with where the company is headed.
Conclusion
Passages International completed their migration to Odoo with their full financial history intact, reconciled, and verified. Their team entered the new system with an understanding of both the platform and their own data equipped to run reports, manage financials, and operate independently from day one.
The reporting that had been built for their specific business context in NetSuite was not lost. It was thoughtfully re-engineered inside Odoo, giving them the same business visibility in a more flexible, more affordable, and more modern platform.
And unlike migrations that treat the go-live as the finish line, Bayforward ensured Passages International was enabled on Odoo not just transitioned to it. There’s a meaningful difference between an organization that can use a system and one that’s truly empowered by it.
Table of Contents
Talk to Our Team
Share your email for a quick, personalized response.
Get in Touch with Us
Our team of experts, engineers, and innovators is ready to collaborate with you.
