WordPress migration & hosting

The problem isn't WordPress, it's the chain

When hosting, DNS, cache and plugins get managed in pieces, every slowdown becomes a blame hunt.

• 01

  Slow shared hosting

  The site loads in eight or ten seconds because it lives on a packed server, with contended resources and random cache. Then someone says WordPress is heavy. Convenient.

• 02

  Badly done migration

  A host switch without staging can break images, permalinks, redirects and tracking. The site comes back online, but with dead pages and wounded organic traffic.

• 03

  SSL and DNS ignored

  When certificates, records and domain don't have a clear owner, one expiration or one wrong change is enough to take everything offline.

1. 01

   Migration without darkness

   The site gets copied and tested on staging before the switch. The transition happens when hosting, database, files, redirects and SSL are ready, so visitors don't find broken pages or white screens.

2. 02

   Tuned WordPress hosting

   I choose and configure an environment suited to the site: WP Engine, SiteGround or optimized hosting. No shared servers full of unknown sites slowing every request and wasting visitors' time.

3. 03

   DNS and SSL handled

   DNS switch planned with TTL, correct records and active SSL certificates. No domain hanging between old and new host while everyone says it depends on someone else.

4. 04

   Clean CDN and cache

   I configure Cloudflare, WP Rocket or equivalent stack without piling up random plugins. Page cache, browser, images and exclusion rules get set up readably, so they don't break carts, forms or restricted areas.

5. 05

   Redirects under control

   I check URLs, media, permalinks and redirects after the migration. Switching hosts shouldn't burn indexed pages, images, tracking or internal links because someone moved files by hand.

6. 06

   Clear final documentation

   At the end, credentials, access, hosting, DNS, CDN and technical notes stay in a tidy document. Whoever manages the site afterwards doesn't have to dig through old emails and chats with vanished providers.

1. 01

   Discovery call

   30 free minutes to understand the real need. I listen, ask questions, take notes. No cold quotes: I need to know what you're actually building first.

2. 02

   Quote

   Flat fee with clear scope, timeline and costs. No surprises: if something falls out of scope I tell you upfront, not when the invoice lands.

3. 03

   Design / Strategy

   Wireframes, moodboard or audit with action plan — depends on the service. You see the direction before any code or content gets touched.

4. 04

   Build

   Development, technical work or operational execution. Agreed check-ins along the way, none of that "let's sync end of month".

5. 05

   Launch & follow-up

   Go-live + 30 days of assistance included. Documentation, training if needed, and an open door for the small things later.

• 01

  Website maintenance

  After the DNS switch you need backups, alerts and controlled updates.

• 02

  WordPress support

  If migration reveals malware or broken plugins, first close the hole.

• 03

  Web Design

  If the site stays old on the new host too, the problem is just moved.

• The questions I hear all the time.

• Does the site stay online during migration?+

  Yes, the goal is avoiding visible downtime. We work on staging, prepare new hosting, and switch DNS only when the copy is ready. There can be a few minutes of technical settling during propagation, but the site doesn't shut down for hours like in improvised transitions.

  What happens if the site has lots of images or heavy plugins?+

  We analyze the real weight first: media, database, plugins, old backups, cache and useless folders. Migration shouldn't carry junk from one server to another without looking at it. Critical parts get copied, tested, and when needed lightened before release.

  Do you also handle domain, DNS and SSL certificate?+

  Yes. DNS and SSL are often the point where the site ends up offline because nobody considers them their own. Records, TTL, certificate, HTTPS redirects and CDN get treated as part of the work, not as a side detail to push onto hosting.

  Can migration damage SEO?+

  It can happen if links, redirects, media or permalinks get broken. That's why I check main URLs, existing redirects, images, canonicals and HTTP responses after the switch. Changing host shouldn't mean making Google find a pile of errors.

  Can I choose the new hosting myself?+

  Yes, if the hosting is suited to the site and doesn't create predictable technical problems. If instead the plan is too weak, too closed or full of limits, I tell you upfront. Better to clarify immediately than migrate to another bottleneck.

  After migration, who keeps the access?+

  Access stays yours. I deliver tidy documentation with hosting, domain, DNS, CDN, WordPress and important technical notes. End of treasure hunt between personal accounts, past agencies and panels nobody knows how to open anymore. You decide.