Managed WordPress hosting for sites leaving InMotion Hosting.
InMotion ships BoldGrid with WordPress: a builder, a backup plugin and a handful of others, installed before you ever logged in. Most of a migration here is deciding what to do with them.
The plugins that were there before you were.
BoldGrid is InMotion's own suite. Some of it is doing real work; some of it is only there because the install put it there.
The BoldGrid builder in your pages
If pages were built with it, the layout lives in its own structures rather than plain blocks. Removing the plugin without checking is how a page turns into unformatted text.
Total Upkeep backups in its own format
BoldGrid's backup plugin writes archives only it can restore. They are not a migration route on their own, and relying on one is how a move stalls.
Cloud WordPress staging copies
InMotion offers throwaway staging sites outside your account. Anything only living there does not appear in a cPanel backup and has to be collected separately.
A cPanel account underneath
Beneath the WordPress layer this is ordinary cPanel, which means addon domains, panel cron and mailboxes can share the account.
Their security plugins
Preinstalled security and performance plugins overlap with what the platform does here. Keeping both means two things fighting over the same headers and caches.
Decide about BoldGrid before you copy anything.
Whether the builder is load-bearing decides the shape of the whole migration. It is a five-minute check that changes everything downstream.
- Pages checked for BoldGrid builder content
- Total Upkeep archives converted, not relied on
- Cloud WordPress staging collected
- Overlapping plugins retired on arrival
Fewer plugins doing the platform's job.
A preinstalled suite adds caching, security and backup plugins that duplicate what the host should be doing. Retiring them is most of the gain.
What we change when a site arrives from InMotion
Nearly all of it concerns software that arrived with the install rather than by choice.
| Setting | What we do | Why |
|---|---|---|
| BoldGrid builder | Page content checked for builder structures before the plugin is touched | Pages built with it store their layout in its own format, so removing it first turns a designed page into unformatted text with no undo. |
| Total Upkeep archives | Converted rather than used as the migration route | Its backups are written in a format only that plugin restores, so treating one as a portable archive produces a file the destination cannot open. |
| Cloud WordPress staging | Collected separately from the production account | Those staging copies live outside the hosting account entirely, so nothing in a cPanel backup contains them and recent work there is simply missed. |
| Bundled plugins | Security, caching and optimisation plugins retired where the platform covers them | Keeping a plugin that sets the same headers and caches the platform already manages leaves two systems disagreeing about the same request. |
| cPanel account contents | Addon domains, panel cron and mailboxes enumerated | The managed WordPress layer sits on an ordinary cPanel account, which regularly holds a second site or a mailbox nobody remembered. |
Simple, transparent pricing.
Every plan includes free migration, daily backups, SSL and 24/7 support.
- 1 WordPress site
- 10 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Support tickets
- 5 WordPress sites
- 50 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Priority support tickets
- 20 WordPress sites
- 200 GB NVMe disk
- Free SSL
- Daily backups
- One-click deployment
- Dedicated support
Questions, answered.
Can I just delete BoldGrid before migrating?
I have Total Upkeep backups. Can you migrate from those?
What about my Cloud WordPress staging site?
Do I need the security plugins that came preinstalled?
Is InMotion cPanel hosting underneath?
Keep the site, retire the bundle.
Free migration, BoldGrid checked before it is removed, and staging copies collected too.