If you're on Oracle Commerce, the platform has probably been carrying technical debt longer than some of your team has worked there. ATG was excellent in 2008. Oracle Commerce Cloud is a competent platform that's seen quieter investment than peers. The brands moving off it are usually doing so because the code their business runs on hasn't seen meaningful modernisation in a decade. Here's the playbook.
Two platforms, one name
Oracle Commerce isn't one product. The brands considering migration usually fall into one of two camps.
Oracle ATG (Art Technology Group). The original Java-based on-premise commerce platform Oracle acquired in 2010. ATG was a leader through the late 2000s and 2010s, particularly in B2B and complex commerce. Most ATG customers are now running 8 to 15-year-old implementations with significant customisation. Oracle's investment in ATG has been minimal for several years. New ATG implementations are rare.
Oracle Commerce Cloud (OCC). The SaaS rebuild. More modern architecture, REST APIs, headless-friendly. But Oracle's marketing investment in OCC has been quieter than competitors over the last 3 to 4 years, and the customer base is smaller. Some brands have ended up on OCC after ATG migrations and are now considering further migration to Shopify Plus.
The migration mechanics differ between the two. ATG migrations involve more code archaeology, more middleware redesign, and longer timelines. OCC migrations are closer to a Salesforce Commerce Cloud or BigCommerce migration in shape.
Why brands actually leave Oracle Commerce
Three factors drive most Oracle Commerce migrations.
Platform investment trajectory. Customers want to be on platforms that are actively invested in. Shopify Plus ships features quarterly. Oracle Commerce's release cadence is slower, with feature work concentrated in larger releases. For brands competing in fast-moving categories, the velocity gap matters.
Developer talent. ATG developers are increasingly hard to find. Many have moved to other platforms or out of commerce entirely. Maintaining an ATG implementation often means contracting back to former employees or specialist agencies at premium rates. Replacing a senior ATG developer takes 6 to 12 months. Replacing a senior Shopify developer takes 4 to 12 weeks.
Total cost of ownership. A typical mid-market Oracle Commerce environment carries significant infrastructure cost (for ATG) or licence cost (for OCC), plus implementation partner spend, plus the ongoing cost of maintaining customisations. Annual TCO for a $30M to $80M brand on Oracle Commerce often runs $700K to $1.8M, including hosting, partner, and internal team costs. Shopify Plus typically lands at 30 to 50% of that.
Aging surrounding tooling. Oracle Commerce environments often include other Oracle products: Oracle ERP, Oracle Database, Endeca for search, Oracle Identity Cloud Service for authentication. Some of these are also reaching end-of-life or have replacement candidates. Migration becomes a chance to consolidate.
What "the Oracle Commerce stack" actually means
A typical ATG implementation is multi-layered with significant customisation. The migration is part translation, part cleanup.
ATG core. Java-based, configurable through XML and DSP (Dynamo Server Pages). The core doesn't migrate - it's replaced.
Business Control Center (BCC). ATG's admin interface. Replaced by Shopify admin.
Endeca. Oracle's search and merchandising layer. Used for faceted navigation, search results, guided selling, and rule-based merchandising. Doesn't translate directly. Most brands replace Endeca with Algolia, Klevu, Searchspring, or Shopify's native search depending on catalogue size and filtering needs.
ATG Web Commerce. The customer-facing storefront framework. Doesn't migrate. The front-end gets rebuilt as classic Shopify Plus theme or Hydrogen headless.
ATG B2B Commerce. The B2B-specific module. Maps to Shopify Plus B2B with workflow rebuild.
Personalization Module. ATG's rule-based personalisation engine. Replaced by Shopify Functions, Shopify Scripts (legacy), or apps depending on use.
Promotion Module. ATG's promotion engine. Translated to Shopify Discounts, Functions, or apps depending on rule complexity.
Custom modules. Most ATG installs have years of bespoke modules. The audit during Phase 1 determines which become Shopify Functions, which become apps, which get replaced by native features, and which get retired.
The integration problem
Oracle Commerce environments are usually deeply integrated. ERP (often Oracle ERP), order management, fulfilment, payment, tax, customer service tooling, and bespoke connectors built years ago.
Two patterns are common.
Direct integration via Java. ATG implementations often have direct Java-based integration to ERP and other systems. These don't translate to Shopify directly. The connection logic needs to be rebuilt against Shopify APIs, usually with a middleware layer (Boomi, MuleSoft, Workato) added during migration.
Middleware-routed integration. Some Oracle Commerce environments already have middleware in place, particularly the more recent Oracle Commerce Cloud installs. The middleware can usually be repointed at Shopify with mapping changes rather than full rebuilds.
A typical Oracle Commerce migration includes 5 to 12 integration workstreams. Each one is its own project. ERP integration alone often runs 8 to 12 weeks parallel to the rest of the build.
What changes at the data layer
ATG uses a flexible repository-based data model. Products, SKUs, customer profiles, and orders are stored as repository items with configurable properties. The translation is documented in catalog mapping before any data moves.
Products and SKUs. ATG's product/SKU model maps to Shopify's product/variant model. Most translations are clean. Configurable products with deep variation depth (especially in B2B catalogues) need explicit mapping decisions.
Categories. ATG category trees can be deep, multi-rooted, and shared across catalogues. Shopify uses flat collections by default. The migration usually maps the primary category hierarchy to navigation, with collections driven by tags or rules.
Customer profiles. ATG customer profiles include contact information, addresses, account preferences, and B2B organisation membership. These map to Shopify customer records and Shopify B2B companies. Passwords don't migrate (see customer account migration).
Order history. ATG orders include line items, payment information, shipping, fees, returns, and order state. All of it migrates. Custom order metadata that fed downstream systems gets reviewed during migration.
Pricing and promotions. ATG's pricing engine is rules-based and can be complex. The translation usually involves Shopify Discounts for simpler patterns, Shopify Functions for complex pricing logic, and apps for promotion campaigns that don't fit native patterns.
Endeca data. Endeca-driven search and merchandising data needs to be re-modelled for the replacement search platform. Faceted navigation rules, merchandising boost rules, and synonym lists usually need to be rebuilt rather than migrated, because the underlying engines work differently.
B2B migration
ATG was historically strong in B2B. Many ATG customers run B2B-heavy or B2B-only stores. The Shopify Plus B2B platform has matured but the workflow translation needs care.
What translates cleanly:
What needs more work:
For brands where B2B is more than 50% of revenue (common for ATG), the B2B workflow audit deserves a dedicated discovery phase.
The SEO conversation
ATG URL structures are highly configurable and often customised. Older implementations may have URL patterns like /category/cat-id/product-id or include session-state parameters. Newer implementations and Oracle Commerce Cloud use cleaner patterns.
Shopify uses /products/handle, /collections/handle, /blogs/blog-name/article-handle, /pages/handle. The 301 redirect map handles the transition.
For Oracle Commerce stores the redirect map is usually 15,000 to 150,000 URLs. The volume comes from accumulated content over years, multi-region setups, and faceted navigation URLs that have been indexed. We crawl the live site, pull Google Search Console data covering the last 12 months, and pull existing redirect rules into a source-of-truth spreadsheet before mapping destinations.
ATG sites often have legacy URLs from implementations 8+ years ago that are still indexed. These show up in the GSC data and need destinations on the new site. Skipping them costs rankings on long-tail queries.
Timeline reality
Most Oracle Commerce to Shopify Plus migrations run 16 to 24 weeks. Same range as SAP Commerce Cloud, longer than other source platforms.
Breakdown:
What stretches the timeline: ATG custom module count above 30, ERP integration complexity, B2B above 50% of revenue, complex CPQ requirements, and any aging surrounding Oracle systems being replaced in parallel.
What we won't do
A few principles that keep the project clean.
We don't try to replicate every ATG customisation. Most ATG installs have 30 to 100 custom modules. The audit usually shows 50 to 70% have no real impact or can be retired with the migration. We don't replicate dead code.
We don't try to lift Endeca. Endeca's data model and search behaviour don't translate to other platforms. The replacement (Algolia, Klevu, native) is configured fresh based on the live merchandising rules and search queries, not by copying configurations.
We don't ship until ERP integration is rehearsed end-to-end. The integration runbook is executed against staging endpoints with sample data on the migration sandbox before go-live.
We don't ship without B2B workflow sign-off. Sales operations teams test the full B2B purchase journey on staging.
We don't ship without 1:1 reconciliation. Product count matches. Customer count matches. Organisation count matches. Order count matches. If anything doesn't reconcile, we don't launch.
We don't sign off on a redirect map we haven't tested. Every URL gets crawled. Every redirect gets verified. Long-tail URLs from older ATG implementations get their share of attention.
Where to start
If you're considering an Oracle Commerce or ATG migration to Shopify Plus, the first step is a discovery audit. We document your custom modules, integration architecture, B2B structure, Endeca configurations, and redirect surface area, then return a build spec, a risk register, and a fixed-price Phase 1 quote.
The dedicated Oracle Commerce to Shopify Plus migration page has more detail on our process, what's included, and how the timeline maps to your specific setup.
For broader context on Shopify Plus migrations across all source platforms, see the complete migration guide. For the operational architecture that makes a Shopify Plus migration pay back, why your Shopify Plus store needs an operations strategy and your Shopify tech stack is growing cover the layer that determines whether the new platform actually delivers.
Frequently asked questions
Why are brands leaving Oracle Commerce in 2026?
Three drivers. First, Oracle's strategic direction has shifted away from commerce-as-a-product, with most enterprise focus on cloud infrastructure and database. Second, the developer talent pool for ATG and Oracle Commerce has shrunk significantly over the last 5 years, making maintenance increasingly expensive. Third, Oracle Commerce stores tend to have years of accumulated customisation that's hard to update or extend without specialised consultants.
What's the difference between ATG and Oracle Commerce Cloud?
ATG (Art Technology Group) was the on-premises platform Oracle acquired in 2010. Oracle Commerce Cloud is the SaaS version. Both share the same core data model but have different integration architectures. ATG migrations are usually more complex because the on-premises customisation depth is typically greater than Cloud customers. Both migrate to Shopify Plus with similar workflow translation work.
How long does an Oracle Commerce to Shopify Plus migration take?
Most Oracle Commerce migrations run 16 to 24 weeks, similar to SAP Commerce Cloud. The variance is driven by the depth of customisation, the number of legacy integrations, and whether Endeca search and Oracle Maxymiser personalisation need replacement. Brands above $50M with deep ATG customisation can push to 24 to 30 weeks.
What happens to Endeca search during migration?
Endeca doesn't transfer. Replacement options for Shopify Plus include Algolia (most common), Klevu, or Searchspring. All three provide enterprise-tier search comparable to what Endeca offered. The migration includes re-indexing the catalogue, rebuilding facet logic, and recreating any custom search rules. Plan 3 to 5 weeks of search-specific workstream.
How does Oracle Commerce B2B translate?
Oracle Commerce has a sophisticated B2B model with organisations, contacts, account hierarchies, and contract pricing. The translation to Shopify B2B is workable but requires explicit rebuild. Organisations become companies, contacts become customers assigned to locations, contract pricing becomes per-company catalogues. The complexity is in the workflow rules attached to entities, especially custom approval logic that ATG environments often have.
What about Oracle Maxymiser personalisation?
Maxymiser personalisation rules don't transfer. Shopify-native replacements include Klaviyo predictive analytics, Nosto, Rebuy, and Yotpo for product recommendations and personalisation. The combined replacement stack typically costs less than Maxymiser and integrates better with the Shopify ecosystem. Plan a 2 to 4 week personalisation workstream to set up replacement tools and migrate audience segments.
How much does an Oracle Commerce to Shopify Plus migration cost?
Build costs typically range from $200K to $450K for mid-market brands, with most landing at $250K to $350K. Oracle Commerce migrations are expensive because of legacy code complexity, custom module rebuild work, and Endeca/Maxymiser replacement. Total year-one investment including post-launch retainer, apps, and integration rebuild usually lands at $450K to $1M.
Should I migrate from ATG before Oracle deprecates it?
ATG isn't formally deprecated, but Oracle's strategic direction makes the writing clear. Most Oracle Commerce brands we work with plan migration on a 12 to 24 month horizon to avoid being the last brand on a shrinking platform. Earlier migration captures the talent pool while consultants who know ATG are still available, and gets ahead of the inevitable cost compression as the ecosystem shrinks.
A Shopify Plus Agency for Strategic Design & Advanced Engineering
Building something ambitious?
- Oracle Commerce migrations are long. 16 to 24 weeks for most stores. Code archaeology and integration redesign are the timeline drivers.
- Two distinct platforms share the Oracle Commerce name: ATG (the on-premise Java platform) and Oracle Commerce Cloud (the SaaS evolution). Migration mechanics differ significantly between them.
- The reasons brands move are platform investment trajectory, developer scarcity, total cost of ownership, and the need to replace surrounding tooling that's also aging.
- Endeca, Oracle's faceted search and merchandising layer, doesn't translate directly. Most stores replace it with Algolia, Klevu, or Shopify's native search depending on catalogue size.
- Migration is also a cleanup exercise. Most Oracle Commerce installs have 8-15 years of accumulated customisation. Migration is the moment to retire what's no longer used.
