Oracle Commerce migration

Oracle Commerce migration:moving to a supported release, or off the platform

If you run Oracle Commerce or ATG, the first question is which release you are on. Oracle's own policy shows 11.3 and earlier past Extended Support, while 11.4 is supported to 2029. We help you work out what that means, then plan the upgrade or the move away.

Discuss your Oracle Commerce storeSee all migrations

Where Oracle Commerce stands, as of October 2026

From Oracle's Lifetime Support Policy for Applications (August 2026), its support policies and its customer community.

  • 11.3 and older: Sustaining Support only

    Oracle Commerce 11.3 left Premier Support in April 2022 and Extended Support in April 2025. Oracle's policy says Sustaining Support brings no new fixes, security alerts or critical patch updates.

  • 11.4 is supported to 2029

    Released in July 2024, with Premier Support to July 2029 and Extended Support to July 2032. ATG 9 and 10, and Commerce 11 to 11.2, are all long past their Extended Support dates.

  • It is not end of life

    In July 2026, Oracle's community post described continued investment in ATG and Endeca, with a new release targeted by the end of 2026. Sustaining Support dates are listed as indefinite.

Your three realistic options

Vendors selling a replacement tend to say Oracle has sunset the product. We found no Oracle statement saying so. The choice is yours to make on the facts.

  • Upgrade to 11.4 or later

    Reasonable if the store works well and the customisation is valuable. Oracle says its planned release targets JDK 21 and Jakarta EE 9+, so older custom code will need attention either way.

  • Move to Oracle's cloud commerce product

    Oracle Commerce Cloud is a separate product, still getting releases such as 26D in October 2026. It isn't an upgrade of ATG, so treat it as a migration and judge it as you would any other platform.

  • Move to another platform

    Sensible if the running cost, the shortage of ATG skills or the pace of change is the real problem. Options like Shopify, Adobe Commerce and BigCommerce each need checking against your B2B and catalogue requirements.

  • Stay where you are, for now

    A store on 11.3 still runs. But it gets no new security patches, so we would treat this as a short, deliberate decision, with compensating controls and a date to move.

What makes these migrations hard

Years of customisation, rather than the catalogue itself, drive the size of the job.

  • Custom Nucleus components and repositories

    ATG applications are built from configured Java components and repository definitions. Each customisation has to be kept, replaced by a standard feature or dropped.

  • Search and merchandising in Endeca

    Endeca dimensions, rules and Experience Manager pages have no direct equivalent elsewhere. Moving means replacing the search platform and rebuilding the merchandising rules.

  • B2B accounts and pricing

    Account hierarchies, contract price lists and approval flows have to be mapped carefully, because small differences change what customers are charged.

  • Orders, customers and integrations

    ERP, payment and fulfilment connections all need retesting. Passwords may not transfer, and order history can move in full or be archived. We decide these in the plan.

How we approach an Oracle Commerce move

Decide on the destination only after seeing what you actually use.

  1. Establish the version and support position

    We confirm releases of Commerce, Endeca and your application server against Oracle's policy, and look at what your support contract covers.

  2. Inventory the customisation

    We list custom modules, integrations and merchandising rules, and mark each as essential, replaceable or unused.

  3. Compare the routes on your store

    Upgrade, Oracle cloud and other platforms are compared against that list, with risks and running costs set out, and you make the decision.

  4. Rehearse and cut over in phases

    Catalogue, customers and orders are rehearsed on a test environment, URLs and redirects are mapped, and the cutover plan includes a way back.

How the work is arranged

An assessment comes first, because any price before that would be a guess.

An assessment produces the inventory and a recommendation that you can use whichever supplier does the work. Delivery after that is priced in phases, and supporting developers are available from $20/h in USD, invoiced in USD, GBP, EUR or INR.

We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. The shared hours help with cutover rehearsals alongside your operations and ERP teams. Other destinations are covered on our Shopify, Adobe Commerce and BigCommerce migration pages.

Why no Oracle Commerce stores are named

Most of our work is delivered under NDA, so many projects cannot be named.

Stores on this platform are usually large organisations with strict rules about disclosure, so this page makes no claims about them. It describes how we would assess your store instead.

Questions about Oracle Commerce

Asked by teams working out what to do next.

Has Oracle ended Oracle Commerce?
No, not according to anything we found from Oracle. Its lifetime support policy lists 11.4 with Premier Support to July 2029, and a July 2026 community post describes continued investment. Older releases are a different matter, so check yours.
What does Sustaining Support mean for us on 11.3?
Oracle's support policy says it keeps access to what already exists, but no new program updates, fixes, security alerts or critical patch updates, and no new certifications with third-party products.
Is Oracle Commerce Cloud an upgrade from ATG?
No. It is a separate product with a different architecture, so custom code doesn't carry over. It should be judged as a migration, alongside other platforms.
Should we leave, or upgrade to 11.4?
It depends on how much of your customisation still earns its keep, what it costs to run and whether you can hire people who know it. We would rather answer that after an inventory than guess now.

Which release are you on?

Tell us the Commerce and Endeca versions, and roughly how much custom code you have. We will explain your support position and sensible next steps.

Start an Oracle Commerce conversationSee all migrations

We reply within one business day (IST).