Replacing WordPress is worth discussing when the current site is difficult to manage, no longer presents the business well or cannot support the customer flow you need. Start by identifying the useful parts to retain.
A new design can still cost you useful work if old service links break, quote requests stop arriving or a domain change interrupts business email. Put those dependencies in the quote before choosing the new platform.
If the problem is a neglected update or one broken feature, ask whether repairing it is the sensible first step. Commission a rebuild when its scope addresses the problem you have identified.
Inventory the useful pages and their addresses
List the service pages, project stories, articles and downloads you want to keep. Include pages that receive enquiries or have links from other sites, even if they are missing from the main menu. Search Console, analytics, the sitemap and the existing content list are useful inputs. No single one is a complete inventory by itself.
Keep existing URLs when they still fit. For an address that changes, record the most relevant replacement. A service page should lead to its new equivalent rather than send every old link to the homepage.
Google's site-move guidance explains URL mapping and redirects, and warns that search rankings can fluctuate during a move. Redirect planning gives existing links a destination. Allow for monitoring search performance after launch.
List what your plugins actually do
You do not need to reproduce every plugin. You do need to account for the business function each one supports.
Write down forms, bookings, payments, customer accounts, gated downloads, redirects and content editing. For each, identify what the customer does, where the records are stored and who operates it. A plugin used only to create a layout is a different dependency from a plugin holding paid orders.
Some functions can stay in their existing external service. Others need a replacement or a data migration. Ask the supplier to state which route is proposed and what, if anything, will stop being available.
Keep the domain and email arrangements visible
Confirm who controls the registrar and DNS accounts, and how the business can recover access. Moving the website does not necessarily mean moving the domain registration or business email.
Give the supplier a record of the services connected through DNS. Website records, email delivery records and service-verification records can all share the same zone. Ask for the planned changes and a way to reverse them if the launch fails. Do not cancel the existing hosting account before the new site and any remaining dependencies have been checked.
Your domain remains an operating cost. At noboringsites, domain registration and renewal are separate from a build or hosting plan.
Agree what “ready to launch” means
For a service website, start with the path that brings work into the business. A visitor should be able to find the relevant service, understand it and make the agreed enquiry. The right person should receive that enquiry.
Agree a labelled test with the supplier. Check the confirmation, delivery destination and any connected CRM record using test details. A visually correct form does not establish that delivery works. Where a site takes money, include an agreed test-mode purchase and the fulfilment it should trigger.
Check the migrated content, important old links, redirects and mobile controls too. The preview should have its search visibility controls removed only as part of the agreed launch. Keep a recoverable copy of the old site and the data needed to operate it.
Put the handover in the proposal
Ask what you will receive: delivered code and content, access to the editing system, exported records where applicable and the information a future supplier would need. Clarify the ownership and licence terms for your route.
For a noboringsites custom build, the Terms assign copyright in the bespoke delivered design and content at handover after full payment, subject to the retained tooling described in the Terms. A template is separately licensed per live site. The terms and template licence set out those arrangements.
Decide who maintains the new site and the connected services. Removing WordPress plugins changes the maintenance work; it does not remove the need to maintain software, access and recovery arrangements.
Ask for the migration scope beside the design quote
Request a written answer covering the old-to-new URL map, content and data transfer, retained business tools, domain and email dependencies, launch tests, rollback and handover. If an item is excluded, find out who will do it.
Our WordPress comparison and migration overview describe the options. Bring your current URL and the tools you want to keep to a free intro call. That gives us a starting point for scoping the rebuild.
Article tools
Want this done for you?
Bring the process you want to improve, the tools you need to keep or the site you want to move.