Hosting and migration
WordPress to AWS: what changes when you migrate a small business site
Moving a small business site from WordPress to AWS: what happens to hosting costs, speed, security updates, forms, content editing, and the plugins you rely on.
Published Updated 6 min readBy Granite Logic
Moving a small business site from WordPress to AWS usually means rebuilding it as a modern React-based website that AWS serves from a content delivery network, not copying WordPress onto an Amazon server. The site gets faster, there is no WordPress core, theme, or plugin stack left to patch, and the hosting bill for a small site often drops to a few dollars a month. What you give up is the plugin ecosystem and the WordPress editor. Forms, galleries, and anything a plugin did have to be rebuilt, and content editing moves to a simpler editor. If your business runs on WooCommerce, membership plugins, or several staff publishing every day, staying on WordPress is often the better call.
We have done this both ways. We moved Boston Cityscapes, a Boston plantscaping firm, from WordPress to a custom AWS platform with its design intact. We also moved EPS Arts, a fine art gallery, from its old platform to a static site served from AWS. We have also built WordPress and WooCommerce sites for two Finger Lakes vineyards, O·Neh·Da and Eagle Crest, where WordPress fits the job. This guide covers what to weigh before either kind of project.
What does moving WordPress to AWS mean?
There are two very different projects that go by this name.
Lift and shift. WordPress keeps running, just on an Amazon server instead of a shared host. Nothing about editing changes. Nothing about patching changes either: you still own WordPress core, the theme, every plugin, PHP, and the database, plus the server underneath. For a small business this is rarely worth it.
Rebuild. The site is rebuilt as static pages or a Next.js app, and AWS serves it from S3 and CloudFront. The pages are built ahead of time and sent to visitors from servers close to them. No PHP runs when someone loads a page and there is no public database. This is what we mean by a migration, and what the rest of this guide covers.
How does the hosting cost change?
The shape of the bill changes more than the size.
On WordPress you typically pay a flat monthly hosting fee, then yearly renewals for premium plugins: a form builder, a page builder, a backup plugin, an SEO plugin, a slider. Each one is small. Together they add up, and each one is another thing to update.
On AWS you pay for what visitors use. A small brochure site with modest traffic costs very little to serve, often a few dollars a month or less. Plugin licenses go away because the features are built into the site.
The part people forget is that someone has to own the AWS account: keep it secure, watch the bill, renew certificates, run backups. That is a real job. Our Care Plans start at $20 a month and cover hosting, SSL, security updates, uptime monitoring, and daily backups.
Will the site be faster?
Almost always. A WordPress page is assembled on every visit: PHP runs, the database is queried, plugins add their scripts and styles. Caching plugins help, but a site built with a page builder and a dozen plugins usually ships far more code than it needs.
A static site sends a finished page from a server near the visitor. Images can be converted to modern formats and sized for the screen. On a phone over a weak signal, the difference is easy to feel, and it shows up in Google's page experience measures too.
What happens to security updates?
WordPress itself is well maintained. The risk is everything around it. Outdated plugins and themes are the most common way small WordPress sites get hacked, and a site that nobody has logged into for six months is usually running several of them.
After a rebuild there is no login page at /wp-admin for bots to hammer, no database exposed to the public internet, and no plugin queue to keep up with. That removes most of the attack surface. It does not remove all of it. The editor, the form handler, the build tools, and the AWS account all still need care, and the AWS account needs strong passwords and two-factor login. Less to patch is not the same as nothing to patch.
What breaks when you leave WordPress?
Everything a plugin did needs a new home. Before any migration we make a list of every active plugin and decide, one by one, whether its job gets rebuilt, replaced, or dropped. The usual list:
- Contact and lead forms. Contact Form 7, Gravity Forms, and WPForms all go away. Forms are rebuilt and wired to email or a CRM. For Boston Cityscapes that meant HubSpot contact forms and a careers form with resume uploads. Test every form after launch by sending a real message.
- Email. If your WordPress host also ran your email, that needs to move separately, before you switch hosting off.
- Galleries, sliders, and popups. Rebuilt as part of the design, usually with less code than the plugin used.
- URLs. WordPress URLs like /2019/05/post-name/ or /category/news/ need to be kept or redirected, or you lose the search traffic and links pointing at them.
- Comments, site search, and members areas. Each needs a replacement or a decision to drop it.
- Tracking. Analytics, ad pixels, and any chat widget have to be added back.
How do you edit content after the move?
This is the biggest change for most owners, so decide it first.
Most small sites only change a few things often: news, events, staff, photos, opening hours. Those get a simple editor where you fill in fields and upload images. Boston Cityscapes has one for staff profiles and photos. EPS Arts has a custom CMS. Pages that rarely change are edited by your developer, which on a care plan is part of the service.
You lose the freedom to rebuild a page layout yourself on a Tuesday afternoon. Some owners miss that. Most find the site stays tidier without it, and a team that needs to publish often gets an editor with drafts and roles built for exactly that.
What happens to WooCommerce, memberships, and bookings?
They move too. Each plugin's job becomes a piece of the new site that was built for your workflow instead of bolted on:
- WooCommerce becomes a Shopify store, which handles products, payments, shipping rules, and subscriptions without a plugin stack to patch. We set it up and connect it to the new site.
- Memberships, courses, bookings, and directories become part of your custom backend: a screen for each thing you manage, with only the fields you use. No more plugin that almost fits.
- Several people publishing every day get drafts, roles, and approvals in the editor, built around how your team actually works.
A store or membership move is a larger project than a brochure site and gets scoped on its own. It is still a move worth making: the result is a site that fits your business rather than one you keep bending WordPress to approximate.
If your WordPress site is broken or hacked today, fix that first. That is a Website Rescue job, and the migration can start once things are stable.
How does a migration go, step by step?
- List every page, plugin, form, and redirect on the current site.
- Decide what each plugin's job becomes.
- Export the content and images.
- Rebuild the site, keeping the current design if you like it.
- Rebuild the forms and send test messages through each one.
- Map every old URL to its new address.
- Switch the domain over and watch Google Search Console for errors in the first few weeks.
Our services page covers how we handle migrations, hosting, and rescue work. If you are not sure which side of the line you are on, send us your site address and plugin list and we will tell you plainly whether moving is worth it.
Questions people ask
- Is AWS hosting cheaper than WordPress hosting?
- For a small static site, the AWS bill itself is usually a few dollars a month or less, against a flat monthly fee for WordPress hosting plus yearly renewals for premium plugins. The real cost is the person who looks after the AWS side. On our Care Plans that is us, from $20 a month.
- Will I lose my Google rankings if I leave WordPress?
- Not if the move is done carefully. Keep the same URLs where you can, set up permanent redirects where you cannot, and keep page titles and content intact. Expect a small wobble for a few weeks while Google recrawls, then rankings usually settle back.
- Can I keep my current design?
- Yes. A rebuild does not have to mean a redesign. Boston Cityscapes moved from WordPress to AWS with its existing design preserved, so regular visitors saw the same site, only faster.
- Can I still edit my own site after moving off WordPress?
- Yes, for the things that change often. Most small sites get a simple editor for news, events, staff, and photos. What changes is that you fill in fields instead of dragging page-builder blocks around, so the layout stays consistent.
- Do I need to understand AWS to run my site?
- No. You need someone who does. AWS is powerful and easy to misconfigure, so the hosting, backups, and security settings should sit with a developer or a care plan, not with the business owner.