Move forward from WordPressReview first, switch later
Your WordPress site could be the start of your next product. Plan the move in stages: review content and features, build the new project, then switch the domain after testing.
A new project foundation: versioned code and changes you can follow
Move in stagesKeep your current site available
Work on the new project with your AI agent while the existing site continues to run.
01
Understand what you have
List pages, posts, media and URLs. Record the work handled by plugins, forms and custom extensions.
02
Build the new project alongside it
Choose a supported stack. MainPath prepares the repository and pipeline; give the new application a separate test address.
03
Transfer content and features
Map exported content into the new project. Implement the functions you need or connect services you will continue using.
04
Map old URLs to new ones
Plan appropriate redirects and check links, media and important entry pages at the test address.
05
Test, then make the switch
Review the agreed workflows with your team. Change the domain mapping only after acceptance, then check the live site.
Decide before you moveSo you plan the work that matters
Content and media
A WordPress export provides content data. Back up files and the database separately and plan how text, images and attachments will reach the new project.
Plugins and custom features
Themes, page builders and plugin features do not automatically become new application code. Decide what to keep, replace or implement again.
Your publishing workflow
Decide who will edit content afterwards. A repository does not automatically replace the WordPress editor; WordPress can remain part of the solution as a CMS.
URLs and connected services
Include redirects, forms, analytics services and email in the plan. A new website does not mean every DNS record must change.
Build on what you havePlan what moves and what changes
What you can continue using
Text and content data from a WordPress export as a starting point for the transfer.
Existing media, brand content and the domain, with a planned mapping.
WordPress as a CMS for a new interface, if an API connection fits your project.
Presentation: layouts and theme behaviour for the new interface.
Functionality: such as forms, login, a shop or memberships.
The future process for publishing, testing, releases and operation.
A content export is not an automatic conversion of a WordPress project into another stack.
Try the new site firstBefore moving your domain
MainPath gives the new project a process for changes, tests and builds. Review the Dev version and test connections to your services. Replace the existing site only when the move is ready.
Check real examples: forms, links and important user journeys.
Configure access protection for the test environment when you need it.
Release the production version deliberately and check the site after the switch.
MainPath does not automatically convert WordPress into another stack. Your agent checks supported stacks before importing code. A WordPress export can serve as a data source; content, presentation and features must be mapped or implemented for the target project.
Yes, if WordPress remains part of your architecture as a CMS. Its REST API can provide content to a separate application. You set up that connection and the appropriate access for your project.
What happens to a shop, user accounts and memberships?
These areas need their own review. Data, permissions, integrations and workflows must fit the target system. Exporting posts alone does not set them up in the new application.
Can I keep my domain and email?
You can keep the domain. Plan new destinations and redirects before switching. Treat the website and email separately and check which existing DNS records should stay in place.
Moving WordPress files and its database may be the better fit. A new MainPath project is a different decision: it helps you build and release a supported application, without automatically replacing your existing CMS workflow.