Plugin updates and breakage
Every update is a bet that nothing on the page stops working. Owners end up testing their own site after every patch.
Migrate · WordPress
Plan your WordPress move before cutover.
A migration starts with a scoped job in your workspace. Inventory the current pages, posts, media, URLs, and redirects; identify what needs rebuilding; compare the proposed site with the original; then review a cutover plan before changing the domain. Keep the old site live during planning. Search, listings, reviews, content, email, ads, and reports are separate jobs, not automatic actions at signup.
Why now
Why owners leave WordPress
Hosting and security bills nobody understands
Hosting, backups, a security plugin, an SSL renewal, a firewall service. Line items pile up and nobody can say what each one does.
A site nobody works on after launch
The site went live once and has not changed since. No one is assigned to keep it current, so it does not get current.
Process
How to plan the move
- 01
Inventory
Use a WordPress connection or export to inventory pages, posts, media, URLs, and redirects. The current site stays unchanged.
- 02
Scope the rebuild
Map what can move into the workspace and identify missing assets, forms, access, or work that needs a person.
- 03
Review parity
Compare proposed pages, redirects, titles, images, and forms with the current site and review unresolved gaps.
- 04
Approve cutover
Change the live domain only after the owner reviews parity evidence, hosting costs, and the cutover plan and gives approval.
Scope
What to check before a move
Inventory for the plan
- Pages and posts
- Media, images and files
- Menus and navigation
- Redirects
- Titles and descriptions
- Forms and their delivery paths
Needs replacement review
- Plugins
- Themes
- The admin panel
Check what each one does before deciding how to replace it.
After the move
Review the next site job
After cutover, use the workspace to review work on search, listings, reviews, content, email, and reports. Connected accounts and approvals determine what can be done; a proposal is not a live change.
Migration is a scoped job. Review expected credits and any hosting costs before you begin.
FAQ
Migration questions, answered
01Will my rankings survive the move?
No migration can guarantee rankings. A parity review compares URLs, titles, redirects, and indexability to reduce avoidable loss. Review gaps before authorizing a cutover.
02What happens to my domain?
It stays yours. A proposed cutover changes where the domain points only after you approve the plan and arrange the required access. Nothing moves at signup.
03Do I need to touch my old host?
Keep the old site running during inventory and review. A WordPress connection or export may be needed to inspect content; Carcin should ask for access before reading or changing it.
04What if the audit finds gaps?
The plan names each gap for review. Rebuild or redirect work must be scoped and checked again before cutover; unresolved gaps can block the move.
05Is there a cost for the migration?
A migration can be scoped as a job in your workspace. The free tier includes starter credits; paid plans have fixed monthly prices and included credits. Hosting, third-party services, and optional credit purchases may cost extra. Review the scope and expected credit use before starting.
06Do my images and fonts move too, or just get linked?
The inventory includes images, files, and fonts and checks whether each can move to the destination. Review missing assets and licensing constraints before cutover; do not assume every file transfers automatically.
Feature
Migration, as a feature
Review the move before changing the domain.
Start with your current WordPress site and the work you want done. Review scope, access, expected credits, and the cutover plan before any live change.
Start freeStart free with starter credits · No card required · No automatic cutover at signup