Check software, storage, backups, domain settings and HTTPS before hosting WordPress. Prepare a new website or plan an existing site’s migration and recovery.
List your WordPress and plugin requirements
Decide whether you are preparing a new WordPress website, a WooCommerce store or an existing site to move. List your theme, plugins, integrations and scheduled tasks. Check their current requirements and compatibility before selecting the environment. A plugin may need settings or extensions beyond those needed by WordPress itself.
The configurator provides WordPress or WooCommerce software choices, PHP-version preferences and an HTTPS preference. Compare those choices with your application requirements. Confirm the delivered database version, PHP settings and extension support when access is available; recording a preference in an order does not mean a working site has already been installed.
Count the websites you will operate and estimate space for media, themes, plugins, databases and logs. Existing disk usage is a useful starting point, with room for growth and maintenance. For a store, include product images, orders and any files generated by extensions. Storage size alone does not establish how much traffic a site can serve.
Choose a single-site or multisite preference deliberately. Several independent WordPress installations and a WordPress multisite network need different administration and recovery plans. Do not assume that a multisite choice increases the plan’s site allowance or makes stores share products and orders. Check the plan and your plugins before choosing it.
Choose the update and backup options that suit your project, and read their descriptions in the order summary. Paid extras have separate quotation lines. A configurable option describes the requested service setup; use the delivered service information to confirm what is available.
Keep recoverable copies of both the WordPress files and database, including configuration, media and plugin data. Protect the copies and test restoration in a separate environment. Before changing PHP, a theme or an important plugin, make a recovery copy and check the change away from your live site. Keep access credentials private.
Prepare a new site or a controlled migration
For a new site, organise your domain, content and application settings before launch. Use the actual management details supplied after delivery to complete setup. The existing-domain field records the domain you intend to use; it does not register a domain or configure DNS by itself.
For a move, secure access to the old hosting, files and database before making changes. Prepare and test the destination first. Keeping the same domain differs from changing WordPress URLs; use tools appropriate to WordPress data rather than a blanket database replacement. Multisite moves need a plan specific to the network.
For a live store, plan how to preserve orders and other changes made during the move. Keep a rollback path and the original backups. A migration checklist is not a promise of free migration, zero downtime or unchanged search rankings.
Check pages, media, menus, forms, logins and redirects before switching visitors to the new environment. For WooCommerce, verify the store’s own payment, shipping and order workflows using appropriate test settings. Paying for hosting in crypto does not configure the store’s customer payment gateways.
When the destination is ready, apply the required DNS changes and verify HTTPS, public access and the application after the switch. Keep recovery copies and watch for errors. VPSLibre services have a three-month minimum; review the chosen term, exact crypto invoice and service expiry. Payment confirmation and hosting activation remain separate, and renewal requires a new invoice.