Oracle WebCenter Sites to WordPress Migration

Leave WebCenter Sites
before the 12c deadline

WebCenter Sites 12c leaves Oracle Premier Support in December 2026 and Extended Support in December 2027. Instead of a 14c upgrade, move to WordPress with your assets, URLs, sites, languages and integrations accounted for.

The real problem

Your WebCenter Sites platform works. Keeping it is the project.

The sites publish and the content is governed. What slows you down is that every new page layout is a template a developer writes, and the specialists who know those templates are a small pool.

Now the support dates arrive. Oracle Fusion Middleware 12c, which WebCenter Sites 12.2.1.4 runs on, ends Premier Support in December 2026 and Extended Support in December 2027. Staying means a 14c upgrade of the application and the stack beneath it, scoped, tested and paid for, with Oracle annual support paid on top.

Still weighing the platforms? Compare WordPress and WebCenter Sites.

What the migration covers

Everything that has to survive the move

A migration is not a content export. These are the six layers that decide whether the new site behaves like the old one on launch day.

  • Asset model mapping

    WebCenter Sites asset types, attributes and definitions become WordPress post types, fields and taxonomies, mapped during discovery so each asset lands where your editors expect it.

  • Templates and page layouts

    Developer-built templates become blocks and patterns your editors place themselves. Layout stops living in template code and starts living in the editor, inside approved designs.

  • Media and documents

    Images and documents stored as assets import first, with duplicates removed. A second pass rewrites every reference in the content, so no image or link breaks after launch. Indexed files get their own redirects.

  • URLs and redirects

    WebCenter Sites can serve the same page through vanity URLs and older asset addresses. The redirect map is built from a full crawl that captures all of them, and one rule holds: no redirect chains.

  • Integrations

    Each connection to your other systems is reviewed in the diagnosis and sorted: replaced by a WordPress plugin, rebuilt as custom code, or retired. Forms, CRM, marketing automation and analytics are rebuilt and tested before the switch.

  • Sites, languages, users and roles

    Each site and each language comes across with its translations linked. Users and their roles map onto WordPress roles, with authors kept on their content.

AI in migrations

Agents map your assets before anything moves

WebCenter Sites keeps content in asset types, attributes and templates. Agents read that structure, propose where each piece lands in WordPress, and your team approves the map.

  • Field-level extraction

    Assets, attributes and media are extracted into a shared sheet you review with us.

    In use
  • Two to three months without a redesign

    Agents carry most of the content mapping, which is what used to make CMS moves long.

    In use
  • AI-assisted testing

    Compares each migrated page with its WebCenter Sites original and flags what changed.

    In development
Read: what it costs to stay on your current platform

AI suggestion

Migration mapping · example

Legacy component
Promo asset with image, headline and link attributes
Proposed block
Cover block with one primary button
Note
Attributes mapped one to one. Alt text drafted for review.

Nothing moves unreviewed

What changes

From “send it to the template team” to “it’s already live”

After the migration, the people who write the content are the people who publish it.

Editors assemble pages from approved blocks and see the result as they work. Updates are planned into the monthly work instead of a middleware upgrade every few years, and there is no license to renew. Your developers go back to work that needs developers.

Not Oracle, but the same problem: Ueno Bank left Liferay, another Java enterprise platform, for WordPress VIP and launched in weeks, with marketing publishing on its own. Read the case

Team reviews CMS migration plan in office

The plan

How the migration runs

Three steps, with a decision point at the end of each one. Your WebCenter Sites platform stays live until the new site is verified.

  1. Step 1

    Diagnose

    A full crawl of your sites, an asset and template inventory, an integration review and a baseline of every URL, canonical tag and metadata value. Then a pilot: a real slice of content migrated end to end, so the mapping is proven before the full run.

  2. Step 2

    Build or migrate

    Frontend, backend and content migration run in parallel while WebCenter Sites stays live and editable. QA covers browsers, integrations, languages and the editor workflows, tested with the people who will use the CMS.

  3. Step 3

    Operate

    Cutover with the previous platform kept available, so rollback is a decision rather than a project. We watch rankings and coverage until they settle, and keep improving the platform with your team.

Before you commit

See what your migration actually involves

In 30 minutes we look at your sites, your asset types and your integrations, and tell you what moving them involves compared with the 14c upgrade. No obligation to go further.

FAQ

What teams ask before leaving WebCenter Sites

The questions teams ask before they decide, answered plainly.

Ready when you are

Put the 14c upgrade budget into a move

Bring us your WebCenter Sites setup and we will map the path off it: assets, redirects, integrations, sites, languages, and the workflows your team will use on day one.