WordPress Theme Migration: Switch Themes Without Leaving Shortcodes or Rankings Behind

What breaks the moment you click Activate

A theme switch looks like one click in Appearance > Themes. On a simple blog it nearly is. On a site built with a theme's own builder, that click separates the content from the code that knew how to draw it. Here is what typically goes wrong, in roughly the order owners notice.

• Builder shortcodes print as text. Divi 4 stores layouts as et_pb_ shortcodes, Avada's builder uses fusion_ shortcodes and WPBakery uses vc_ ones. Without the builder, visitors read the brackets. See Divi shortcodes showing after a theme change and WPBakery shortcodes showing as text.
• Customizer settings stay behind. Colors, fonts, logo sizes and header layouts are saved per theme, so the new theme starts from its own defaults.
• Menus and widgets lose their places. Menu locations have different names in every theme, and widgets in areas the new theme lacks go inactive.
• Theme-built headers and footers vanish. A header made in Divi's Theme Builder or Avada's Layout Builder belongs to that theme and leaves with it.
• Theme-registered content disappears. Some themes register their own portfolio or project post types. Switch away and those URLs return a 404.
• Quiet SEO changes. Breadcrumbs, schema and heading markup the old theme printed may simply not exist in the new one.

None of this is a reason to stay on a theme you have outgrown. It is a reason not to switch on a Friday afternoon on the live site. Every item above can be found in advance, listed and handled on a staging copy, so the version your customers see changes once, finished, instead of breaking in public while someone hunts for the old settings. If a switch has already gone wrong, our theme repair team can roll it back first.

Choosing where the site moves to

The destination matters more than the move. A lightweight classic theme with a header builder suits a team that likes the Customizer. A block theme suits a team ready to work in the Site Editor with patterns. Another heavy builder suits nobody who is leaving a builder because of its weight. Before recommending anything, we look at who edits the site, how often, and what they actually change.

Our roundup of lightweight WordPress themes compares more candidates, and the full set of theme reviews covers pricing, builders and known problems for each. Classic destinations get a child theme from day one, so any custom code survives the new theme's updates.

Cleaning out years of shortcodes

Shortcode cleanup starts with a count, not a delete key. We search the database for every builder shortcode and list which pages use them, how heavily, and how much traffic each page brings in. That list sorts the site into three piles: pages worth rebuilding by hand, pages whose text can be lifted out of the brackets into clean blocks, and pages that should retire with a redirect. It is the same method we use for moving WPBakery content to the block editor.

Each builder brings its own wrinkles. Divi 5 dropped shortcodes for a block-based format, and Divi 4 sites move with the vendor's Divi 5 Migrator, but third-party modules that aren't ready stay in a backward-compatibility mode and show raw shortcodes if their plugin is switched off. Avada's documentation says a page made in Gutenberg can't be edited in Avada Builder, and the reverse. Bricks converts to block-editor data only for core WordPress blocks. Text survives these moves. Layout never does.

The search traffic you earned stays put

Changing themes doesn't change your permalinks, because URLs are a WordPress setting, not a theme setting. That is the good news. The catch is that rankings depend on more than addresses, and a theme touches a lot of what Google reads. We crawl the whole site before the switch and again on staging after it, then compare the two reports line by line.

• Titles and descriptions. Some themes print their own. Hello Elementor, for example, can output the excerpt as a meta description alongside your SEO plugin's, which creates duplicates.
• Headings. Builders let anyone style any text as a heading. Each rebuilt page keeps one clear H1 and a sensible outline.
• Internal links and alt text that lived inside builder modules are carried across, not lost with the module.
• Content in tabs, toggles and accordions stays in the page and crawlable.
• Every changed URL, such as an old portfolio post type, gets a permanent redirect. Our redirect guide explains the mapping, and broken-link repair catches anything that slips.

The third option

Athena CMS, with AI agents on staff.

Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.

• PPicassoImages
• AApolloSite analysis
• AAresCompetitor watch
• PPrometheusContent holes
• AAtlasPage depth and structure
• DDelphiAI search visibility

ZDAOAand 12 more agents. Two come with Athena; the rest are monthly add-ons.

Meet the agentsTake the Athena tour

PPicassoWeekly · ImagesAApolloWeekly · Site analysis

Seven steps from old theme to new

1. 1

   Crawl and inventory

   Every URL, template, shortcode, widget, menu, form and theme-registered post type, written down with its traffic.

2. 2

   Build a staging copy

   The migration happens on a private copy. The live site keeps working until launch day.

3. 3

   Install the new theme and a child theme

   Global styles come first: colors, fonts, spacing and breakpoints set once, so every page inherits them.

4. 4

   Rebuild headers, footers and templates

   The parts the old theme builder owned are rebuilt with the new theme's own tools.

5. 5

   Rebuild, convert or retire each page

   High-value pages rebuilt by hand, simple pages converted, dead pages retired with redirects.

6. 6

   Compare before and after

   A second crawl, visual checks on phone and desktop, form tests and a speed run on the same templates as the baseline.

7. 7

   Launch and watch

   The switch happens in a quiet window, then Search Console and analytics are watched for crawl errors and traffic changes in the weeks after.

The uncomfortable arithmetic of a theme switch

Count the builder pages first. If most of your pages are builder layouts, a theme migration means rebuilding most of your pages. That is a large share of the labor of a full rebuild, and at the end you are still on WordPress, with a new theme vendor, a new update schedule and the same plugin stack. For a ten-page brochure site that is a fine trade. For a lead-generation site with dozens of service and location pages, it often isn't.

If the right column sounds familiar, read Divi to Next.js or Avada to Next.js, and the full WordPress to Next.js process. Our page on replacing WordPress covers what you edit with afterward. If you want a new design rather than a copy, that is a Next.js rebuild.

Deliverables, cost drivers and a straight quote

• A shortcode and content inventory, page by page, with the plan for each.
• A redirect map for every URL that changes, tested before launch.
• Before and after crawl reports, so you can see that titles, headings and links survived.
• A documented child theme holding any custom code.
• A short editing guide so your team is at home in the new theme on day one.

What drives the quote: the number of builder pages, how many headers and templates the old theme built, WooCommerce templates, theme-registered post types, and plugins that came bundled with the old theme. Avada, for instance, bundles Slider Revolution, LayerSlider, ACF Pro and others, and each one in use needs a plan. We start with a free site audit, then give you a fixed quote. Financing is available. Prefer a conversation? Call (210) 346-0848.