How to deprecate and migrate a classic theme to full site editing without losing content?

So, you’ve got a good old WordPress theme that’s been chugging along nicely. Maybe it was a gift from a friend, or you built it back in the day. Now you’re hearing about Full Site Editing (FSE) and want to make the switch. The big question, though, is how to do it without losing any of your hard-won content. It’s a totally valid concern, and thankfully, it’s not as scary as it might sound.

The short answer is: you can absolutely migrate your content and content-related settings from a classic theme to one that supports Full Site Editing. It’s more about transferring your existing content and rebuilding the presentation of your site with FSE rather than a direct, one-to-one “conversion” of the theme’s structure. Think of it like moving from a house you custom-built years ago to a brand new, modular home – you bring all your furniture and belongings (your content), but you rearrange and redecorate in the new space.

This guide will walk you through the practical steps and considerations to make this transition as smooth as possible, focusing on what actually matters: keeping your content safe and sound while embracing the power of FSE.

Before diving into the “how,” it’s crucial to grasp the core distinction between these two approaches to WordPress theming. This understanding will prevent a lot of confusion during the migration process.

Classic Themes: The Code-Centric Approach

Classic themes are built around PHP files, template hierarchy, and the familiar WordPress Customizer. They dictate the overall structure and appearance of your site through code.

Template Files: Each page type, post format, or archive has a specific PHP file (e.g., single.php, archive.php, page.php). These files define what content appears and how it’s laid out.
The Loop: This is the heart of classic themes, displaying your post content. How it’s implemented in the PHP dictates how your articles look on the frontend.
Widgets: These are blocks of content that you can place in predefined areas (sidebars, footers) usually managed through the “Widgets” screen in the WordPress dashboard.
Customizer: Provides a visual interface for making limited style and layout adjustments, but it’s still largely dictated by the theme’s code.
Content is Separated from Presentation: Your posts and pages live in the database. The theme’s PHP files tell WordPress how to display that content on the frontend.

Full Site Editing (FSE) Themes: The Block-Centric Approach

FSE themes, powered by the Block Editor (Gutenberg), shift the control from code to blocks. You build your entire site, from headers and footers to individual pages, using the same block interface you use for writing posts.

Template Parts: Instead of individual PHP files for every scenario, FSE uses “template parts” like Header, Footer, Sidebar, which are themselves built with blocks.
Block Patterns: Reusable groups of blocks that allow you to quickly add complex layouts.
Global Styles: A centralized place to define your site’s typography, colors, and overall design elements, all managed through the Site Editor.
Theme.json: A powerful configuration file that acts as the central hub for your FSE theme’s styles, settings, and block support.
Content and Presentation are Integrated: The block editor allows you to design the layout and presentation of your content directly within the block interface. When you save a page or post with FSE, you’re not just saving text; you’re saving a block structure that dictates how it will be displayed.

For those looking to understand the nuances of transitioning from a classic theme to full site editing while ensuring that no content is lost in the process, a related article that provides valuable insights is available at this link. This resource offers practical tips and strategies that can help streamline the migration process, making it easier for developers and site owners to adapt to the new editing capabilities without sacrificing existing content.

The “Migration” Strategy: Content Preservation First

Crucially, when we talk about migrating from a classic theme to FSE, we are not migrating the classic theme’s code or its specific presentation directly. Instead, we are focusing on ensuring your existing WordPress content – your posts, pages, media, comments, and related metadata – remains intact and accessible within your WordPress installation. The “migration” is essentially setting up your new FSE theme and then recreating your site’s look and feel using the block editor, while your content is already there, waiting to be displayed.

Your Content is Safe in the WordPress Database

This is the most important takeaway. Your posts, pages, custom post types, comments, users, etc., are all stored in your WordPress database. They are not intrinsically tied to your classic theme itself. A theme is a set of instructions on how to display that data. When you switch themes, the data remains.

Posts and Pages: All of your written content, images uploaded within the content editor, and metadata are securely stored in the wp_posts and wp_postmeta tables.
Media Library: All images, videos, and documents you’ve uploaded are stored in the wp_uploads folder (organized by year and month) and their database entries are in wp_posts (with post_type set to attachment).
Custom Post Types and Custom Fields: If you’re using plugins to create custom post types (e.g., for products, events) or custom fields (via ACF, Pods, etc.), this data is also usually stored in the wp_posts and wp_postmeta tables and is independent of the theme.

What Isn’t Directly Migrated: Theme-Specific Styling and Layouts

What you’ll need to recreate are:

Homepage Layout: If your classic theme had a specific homepage layout using widgets, custom page templates, or theme options, you’ll need to rebuild this in the FSE Site Editor.
Header and Footer: The design of your header and footer, including navigation menus, logos, and widgets within those areas, will need to be recreated using FSE template parts.
Sidebar Layouts: If you relied on sidebar widgets in specific areas, you’ll need to decide if those areas still fit in your FSE design and rebuild them.
Single Post/Page/Archive Templates: The specific structure and styling of your individual blog posts, pages, or archive pages as defined by your classic theme’s PHP templates.
Theme Options in the Customizer/Theme Settings: Any settings you configured in the WordPress Customizer or via a theme-specific options panel that controlled appearance.

Step 1: Prepare Your Classic Theme and Content

Before making any big changes, it’s wise to get your current site in good shape. This reduces the risk of complications during the transition.

Backup Everything, Seriously

This is non-negotiable. You should always have a full backup of your WordPress site (files and database) before making significant changes. This is your safety net.

Use a Reliable Backup Plugin: Plugins like UpdraftPlus, Jetpack Backup, or BoldGrid Backup make this process simple and automatic.
Manual Backups: If you’re comfortable with it, you can also manually back up your WordPress files via FTP and your database via phpMyAdmin.
Store Backups Off-Site: Don’t keep your backups solely on the same server. Cloud storage or a separate location is best.

Audit Your Existing Content and Theme Settings

Take stock of what you have and what you want to carry over.

Identify Essential Content: Beyond standard posts and pages, list any custom post types, important taxonomies (categories, tags), or user-generated content.
Document Theme Features: What specific features does your classic theme offer that you rely on? This could be unique page templates, custom widgets, or specific shortcodes.
Review Customizations: Have you added custom CSS or made modifications to your classic theme’s files? You’ll need to reapply relevant styles later.
Note Plugin Dependencies: Are there plugins that heavily rely on your current theme’s structure or add content types? Ensure they are compatible with FSE.

Clean Up Unused Content and Media

A cleaner site is easier to manage.

Delete Old Drafts and Revisions: Trim down unnecessary post revisions and old draft pages.
Remove Unused Plugins and Themes: Deactivate and delete any plugins or old themes you are no longer using. These can sometimes cause conflicts or slow down your site.
Optimize Your Database: Plugins like WP-Optimize can help clean up your database by removing spam comments, trashed items, and other bloat.

Step 2: Choose and Set Up Your Full Site Editing Theme

This is where you select your new FSE-compatible theme.

Selecting an FSE-Friendly Theme

Not all themes are built for FSE. Look for themes explicitly designed for it.

Official WordPress Repository: Many modern themes in the official WordPress theme directory now support FSE. Look for tags like “Full Site Editing,” “Block Themes,” or “Site Editor.”
Popular Block Themes:
Twenty Twenty-Two, Twenty Twenty-Three, Twenty Twenty-Four: These are excellent starting points, developed by the WordPress team and fully FSE enabled.
Ona, Blockbase, EditorsKit Block Theme: Other popular and well-supported FSE themes.
Consider a Starter Theme or Framework: If you plan extensive customization, you might look at FSE starter themes designed for developers, though this is a more advanced path.
Check Theme Documentation: Always read the theme’s description and documentation to confirm its FSE capabilities.

Installing and Activating Your New Theme

This is straightforward.

Go to Appearance > Themes in your WordPress dashboard.
Click Add New.
Search for your chosen FSE theme or upload it if you downloaded it as a .zip file.
Click Install, then Activate.

Important: Do not look for FSE theme options in the Customizer anymore. You’ll now manage your site’s design in the Appearance > Editor section.

Initial FSE Theme Configuration (if applicable)

Some FSE themes come with pre-built starter templates or basic configurations.

Starter Templates: Many FSE themes offer importable “starter templates” that give you a foundation to build upon. You can apply these to get a head start on your layout.
Global Styles: Familiarize yourself with the Global Styles panel within the Site Editor. This is where you’ll set your site’s typography, colors, and general design system, which will then be applied consistently across your site.

When considering the transition from a classic theme to full site editing, it’s essential to understand the broader context of website management and migration. A related article that provides valuable insights on server migrations can be found here, which discusses the process of migrating to another server. This resource can help you grasp the technical aspects involved in moving your site, ensuring that you maintain content integrity throughout the transition.

Step 3: Rebuilding Your Site’s Structure with the Site Editor

This is the core of the FSE “migration” process. You’ll be using the block editor in a new way to design your entire site.

Accessing the Site Editor

The Site Editor is your new control panel for FSE themes.

Go to Appearance > Editor.
This will open the full-site editing interface, showing you a live preview of your site with editing controls.

Understanding Template Parts

Template Parts are the building blocks of your FSE theme’s structure.

Header: Contains your site title/logo, navigation.
Footer: Contains copyright info, links, widgets.
Sidebar: If your layout includes one, its content and design.
Post Content: The area where your individual post or page content will be displayed.

How to Edit: Navigate to Appearance > Editor, then click the WordPress logo in the top left corner to reveal the left-hand sidebar. Here you can select Template Parts and start editing them.

Recreating Your Homepage Design

This is often the most complex part, as classic themes had flexible homepage setups.

Identify Content Blocks: Think about what content used to be on your homepage (e.g., latest posts, featured content, welcome message, calls to action).
Use Page Editor for Homepage Content: When you go to Pages > All Pages and edit your established homepage, you will now be using the Block Editor to arrange these blocks directly on the page. For example, you might use the “Latest Posts” block, “Image” block, “Heading” block, and “Button” block.
FSE Template Hierarchy and Homepage: For more complex homepage layouts that might have been defined by a front-page.php or home.php in a classic theme, you’ll find that within the Site Editor, you can edit “Templates” themselves. The “Homepage” template will control the overall structure of your homepage when it’s set to display your latest posts, or a static page. If you use a static page as your homepage, the blocks you add to that page in the Block Editor will appear within the content area defined by the site’s header and footer template parts.

Designing Your Navigation Menus

Menus are now handled differently.

Navigation Block: In FSE, you’ll primarily use the Navigation block within your Header template part.
Creating a New Menu: Within the Site Editor, edit your Header template part. Add or select the Navigation block. You can then start adding links directly within the block. You can link to pages, posts, custom links, or categories.
Syncing with Existing Menus: If you have existing menus created under Appearance > Menus in your classic setup, you can either recreate them within the Navigation block or, if your FSE theme supports it and you’re migrating content, there might be an option to select an existing menu from the block’s settings. However, it’s often cleaner to rebuild your navigation using the Navigation block directly within the FSE environment.

Customizing Post and Archive Templates

This is how your individual blog posts and lists of posts will look.

Edit Post/Archive Templates: In the Site Editor, go to Templates. You’ll see options like “Single Post,” “Archive,” “Index,” etc. Select the template you want to customize.
Block for Post Content: Within these templates, you’ll find blocks like “Post Title,” “Post Content,” “Post Date,” “Author,” etc. These are dynamically pulled from your content.
Layout and Styling: Arrange these blocks to control the layout of your posts. Add elements like featured images, comments, or social sharing buttons using relevant blocks.
Block Patterns for Consistency: Create block patterns for recurring elements (e.g., author bio, call-to-action box) to ensure consistency across your posts.

When considering the transition from a classic theme to full site editing, it’s essential to understand the nuances of content migration to ensure nothing is lost in the process. A helpful resource that delves deeper into this topic is an article that provides insights on effective strategies for theme deprecation and migration. You can explore it further by visiting this link, which offers valuable tips and best practices for a seamless transition.

Step 4: Migrating Specific Content Elements and Settings

While your major content is already in the database, some specific elements might need manual attention.

Rebuilding Custom Page Templates

Classic themes often offered custom page templates (e.g., “Full Width,” “Contact Page”).

FSE “Templates” vs. Classic “Page Templates”: In FSE, custom page layouts are achieved by creating or modifying “Templates” within the Site Editor.
Creating a New Template: Go to Appearance > Editor, then click the WordPress logo, select Templates, and click “Add New.” You can then build this template using blocks.
Assigning Templates to Pages: To use this new template for specific pages, go to Pages > All Pages, edit the desired page, and in the Page settings sidebar, look for “Template” and select your newly created FSE template.

Handling Widgets and Widget Areas

Widgets from classic themes don’t directly translate to FSE.

Widget Areas Become Template Parts: Think of your classic widget areas (like sidebars or footer columns) as areas you want to populate with content blocks.
Rebuild in Site Editor: Edit the relevant Template Part (e.g., Header, Footer, or a dedicated Sidebar template part). Add blocks where you would have previously added widgets.
Block Widgets: If you want specific widget functionality (like a search bar or archive list), look for their block equivalents. The core WordPress block library includes blocks for many common widget types.
Plugin Widgets: If plugins provided custom widgets, check if those plugins now offer block-based versions or if they integrate with FSE template parts.

Migrating Custom Fields and Meta Boxes

If you use custom fields (e.g., with ACF, Pods, Meta Box), this data is still in your database. The challenge is displaying it.

Plugin Support for FSE: Many popular custom field plugins (like Advanced Custom Fields) have been updated to support FSE. They provide blocks that allow you to dynamically display your custom field data within the Site Editor.
Dynamic Blocks: Look for blocks offered by your custom field plugin that can pull and display specific meta fields. You’ll add these blocks to your post templates or pages in the Site Editor.
Manual Display (for Developers): If your plugin doesn’t offer a block, you might need a developer to create a custom block or modify PHP templates to display the data.
Ensure Plugin Compatibility: Always check that your custom field plugins are updated and explicitly state they are compatible with FSE.

Reapplying Custom CSS

If you had custom CSS in your classic theme’s “Additional CSS” or a child theme, you’ll need to reapply it.

Global Styles Panel: For many design elements (colors, typography, spacing), you can set these in the Site Editor > Global Styles. This is the preferred FSE method.
Additional CSS (Temporary): You can still add custom CSS via Appearance > Customizer > Additional CSS for now. However, as FSE themes become more mature, you might find CSS is managed more holistically within the theme’s theme.json or through dedicated block styling.
Block-Specific CSS: Sometimes you might need to target specific blocks. You can often add custom CSS classes to blocks in the Block Editor and then target those classes in your Additional CSS.

Step 5: Testing and Launching

Thorough testing is essential to ensure everything looks and works as expected.

Thoroughly Test Your Site

This is not the time to skip steps.

Frontend Testing: Browse every page, post, and archive on your site.
Content Display: Is all your text, images, and other media appearing correctly?
Layout and Responsiveness: How does it look on different screen sizes (desktop, tablet, mobile)? Ensure your blocks are stacking or adapting gracefully.
Navigation: Do all your links work? Is the navigation intuitive?
Forms: Test any contact forms, comment forms, or search bars.
Functionality: Are any interactive elements (sliders, accordions, galleries) working correctly?
Backend Testing:
Editor Experience: Can you easily edit your pages and posts using the Block Editor?
Site Editor Experience: Can you navigate and make changes in the Site Editor without errors?

Check for Broken Links and Images

Use online tools or plugins to scan your site for broken links and missing images.

Broken Link Checker Plugins: Plugins like “Broken Link Checker” can scan your site and alert you to issues.
Google Search Console: This tool can report broken links found by Googlebot.

Gather Feedback

Ask friends, colleagues, or a beta tester group to review your site before you make it public. A fresh pair of eyes can catch things you’ve missed.

Go Live!

Once you’re confident, it’s time to share your updated, FSE-powered site with the world.

If you were on a staging site: Deploy your FSE site from staging to your live environment.
If you were editing live: You’ve already gone live as you made changes!

Final Thoughts: It’s a Rebuild, Not Just a Switch

Remember, migrating to Full Site Editing isn’t like swapping out one paint color for another. It’s more like renovating a room entirely. Your existing furniture (your content) is still there, but you’re reimagining the space with new walls, layout, and decor.

The key to a successful transition lies in understanding that your content is your foundation. By backing up diligently, understanding FSE’s block-centric approach, and systematically rebuilding your site’s presentation using the Site Editor and Block Editor, you can embrace the power of Full Site Editing without losing a single piece of your valuable content. It takes time and patience, but the result is a more flexible, modern, and easier-to-manage WordPress site.