> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://docs.stylecloud.co/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# 1.2.3. What I will need to rebuild

Transitioning from a proprietary web builder (like Wix, Squarespace, Webflow, or others) to WordPress is a smart move if you're looking for more flexibility, scalability, and control. However, migrating isn’t always a plug-and-play process—some elements can transfer easily, while others require a full rebuild.

---

### ${color}[#677a4b](What Stays the Same?)

If your **pages and posts** were already created using the default WordPress Gutenberg Editor (even using a different theme), most of your **core content** should remain intact when switching to Kadence.
* **Pages & Posts** - these are stored in the WordPress database, not the theme. They’ll remain exactly as they were, including permalinks, unless you manually change them.
* **Media (Images, PDFs, etc.)** - the **Media Library** is universal across themes, so your images, videos, and documents won’t disappear. 
* **Menus** - WordPress menus are also global. You may need to reassign them to new Kadence menu locations (like Header or Footer), but the structure and links stay the same.
* **Users, Comments, and Settings**

All of these stay unaffected by a theme change or migration from a builder.

---

### ${color}[#677a4b](What Might Transfer (Depending on the Builder)?)

Not everything is black and white. Some parts of your site *might* transfer depending on your old platform or builder and the tools you use during migration.
* **Galleries & Sliders** - if galleries were created using a **WordPress plugin**, they may transfer over just fine. However, if they were built with a page builder (like Elementor, WPBakery, ACF or a proprietary builder), you may need to rebuild them using Kadence Blocks or install a compatible plugin.
* **Custom Post Types** - if your previous setup included CPTs (like portfolios or testimonials), these might carry over if you used a plugin like CPT UI , or ACF—but you may need to restyle or rebuild the layouts using Kadence Blocks.
* **Shortcodes** - some shortcodes may still function, but if they were tied to a deactivated plugin or old theme feature, they could break or display as plain text. 

---

### ${color}[#677a4b](What Needs to Be Rebuilt?)

This is where the heavy lifting comes in. Some elements are **theme- or builder-specific** and won't migrate cleanly to Kadence.
* **Header & Footer Layouts** - web builders often use proprietary header/footer builders. These won’t migrate directly and need to be rebuilt using **Kadence's drag-and-drop header/footer editor**—which is very flexible, but requires a manual setup.
* **Page Layouts from Visual Builders** - if your previous site used a visual page builder (like Elementor or Divi), the layouts won't look the same under Kadence. While you may reuse some content, you’ll likely have to **rebuild layouts** using **Kadence Blocks**.
* **Custom Styling** - fonts, colors, and spacings tied to your old theme or builder won't carry over. Kadence has its own **Global Color Palette and Typography Settings** which you'll need to configure.
* **Custom Widgets or Sidebars **- some widgets may not work the same or at all. Plan to recreate custom widget areas or use Kadence’s widget-ready elements.

${color}[#f95b45](Use this opportunity to clean up your site structure, update SEO settings, and modernize your design with StyleCloud’s fast and lightweight components.)