Base44 to WordPress: rebuild, split or keep your app

The short version

There is no export from Base44 to WordPress, and no converter can make one. A Base44 project is a React app that talks to Base44’s backend. A WordPress site is built from PHP or block templates that WordPress itself renders. Moving between them means rebuilding, so the useful question is how much to rebuild. There are three sensible answers:

• Rebuild it in WordPress when your Base44 project is really a website: pages, text, images, a contact form, perhaps a blog, and no sign-in.
• Split it when you have both: put the marketing pages in WordPress at example.com and keep the app on a subdomain such as app.example.com.
• Keep the app as it is when the project is the product, with sign-ins, per-user data and logic. WordPress adds little there. If the real worry is ownership or cost, move the app onto accounts you own instead.

The rest of this article helps you tell which case you’re in and walks through each option.

Why there’s no Base44-to-WordPress export

The two platforms build pages in different ways.

A Base44 project downloads as a React app built with Vite, with one file per page in src/pages, components in src/components, and a Base44 SDK client in src/api (project structure). The pages run in the visitor’s browser and fetch their data from Base44’s servers. Our article on exporting Base44 code explains what the export contains and what it leaves behind.

A WordPress theme is made of templates that WordPress renders on the server: HTML block templates and a theme.json file in a block theme, or PHP templates in a classic theme (WordPress Theme Handbook). Your content lives in WordPress’s own database, and WordPress needs hosting that runs PHP with MySQL or MariaDB (WordPress requirements).

A React component isn’t a block or a PHP template, and a Base44 table isn’t a WordPress post type. Nothing translates one into the other automatically. Base44 does document the opposite direction: its migration importer can bring a WordPress site’s posts, pages, categories, tags, comments and media details into Base44. Its docs describe no route back out.

First, work out what your Base44 project is

Many projects have a bit of both: a public landing page, pricing and a blog in front, and a signed-in app behind. That’s the split case.

Option 1: rebuild a content site in WordPress

This fits when your Base44 project is mostly pages. Base44 is also a website builder, and its docs call websites one of the most popular things people build on it (Building a website). If you’d rather have WordPress’s editor, plugins and hosting choices, a rebuild is honest work of a manageable size.

What carries over: your text, images, page structure and URLs, and any records you export as CSV.

What you rebuild: the design. Your React components don’t become blocks, so you recreate the look in a block theme or with a page builder.

Steps

1. List your pages. Base44 publishes every public page in your sitemap at /sitemap.xml (SEO and search visibility). Save it; it’s your checklist and your list of URLs to keep.
2. Export content stored in tables. Blog posts, team members, testimonials and form submissions often live in Base44 tables. Export each one from Data, More actions, Export. WordPress’s built-in importers cover other blogging platforms, not arbitrary CSV files, so a CSV import of posts needs a plugin; WordPress’s import guide mentions one, and WooCommerce imports products from CSV (Importing content).
3. Save your images and files from the app and from the records that link to them.
4. Rebuild the design in a block theme in the Site Editor, or with a page builder such as Elementor.
5. Replace forms with a WordPress form plugin, after exporting the submissions you already have.
6. Keep the same URLs wherever you can. Where a page’s address changes, add a 301 redirect in WordPress so old links and search rankings follow it.
7. Point your domain at the WordPress hosting, check every page, then unpublish the Base44 app. Base44 keeps your data and settings when you unpublish, so you can go back if something is missing. Our article on cancelling Base44 covers the subscription.

Option 2: split the website and the app

This is the most common good answer for a product with a public face. Visitors and search engines see a WordPress site; signed-in users work in the app.

You can split today without leaving Base44. Base44 lets you connect a subdomain such as app.example.com to your app with a CNAME record, while your main domain keeps serving whatever is already there. It issues a certificate for each subdomain you list; wildcard subdomains aren’t supported, and custom domains need the Starter plan or higher as of October 2026 (Connecting a domain).

Steps

1. Rebuild the public pages in WordPress, as in option 1, and leave the app’s pages in the app.
2. Connect app.example.com to the app before you move the main domain, and check sign-in there.
3. Update anything tied to the app’s address. If you use your own Google sign-in client, its authorized JavaScript origin is your app’s domain (Managing login and registration). Payment return pages, links in your app’s emails and links in other services may point at the old address too.
4. Link the two halves. “Sign in” and “Get started” on the WordPress site go to app.example.com; the app’s logo can link back to example.com.
5. Point example.com at WordPress. Base44’s own redirects apply only to domains connected to the Base44 app, so redirects for old app paths (example.com/dashboard to app.example.com/dashboard) belong in WordPress from this point.

The app half can stay on Base44, or move onto infrastructure you own later. The split makes that second move simpler, because the marketing site doesn’t change when the app’s hosting does.

Option 3: keep the app as it is

If your project is a working app, with users who sign in, records they own, functions and automations, rebuilding it in WordPress would mean writing it again on a platform built mainly for content. That’s rarely the goal. People who search for “Base44 to WordPress” often want something else WordPress stands for: their own hosting, their own files, no platform subscription.

That’s an ownership question, not a CMS question. Unbase44 moves the app you already have onto accounts you control: the code into a private GitHub repository in your account, the records into your own database, and the server onto your own Railway account or any Linux server you can reach over SSH. You connect your custom domain from the app’s page, which shows the exact DNS records. You can add a WordPress site or blog in front of it later, as in option 2. The analysis is free and shows what’s in your app before you connect any account or pay.

A stopgap: embedding the app in a WordPress page. You can show a Base44 app inside an iframe on another site. Base44’s security settings let you allow embedding by anyone, only by sites you list, or by no one, and its security scan recommends blocking embedding to protect against clickjacking (Running a security scan). If you embed, allow only your own site. It’s a window onto the Base44 app, not a move: the app still runs on Base44.

Elementor and Shopify

Elementor is a page builder plugin for WordPress (Elementor on WordPress.org). “Base44 to Elementor” is the same job as option 1, with Elementor as the tool you rebuild the design in. There’s no import of React components into Elementor.

Shopify themes are written in Liquid, Shopify’s templating language (Shopify theme architecture), so a Base44 app doesn’t become a Shopify theme either. If your Base44 project is a shop, export your products table as CSV and reshape it for Shopify’s product import, which takes a CSV file (Shopify help). Orders, customer accounts and payment setup need their own plans. As with WordPress, Base44 documents an importer from Shopify, not an exporter to it.

Which option fits