List the flows that create revenue

A shop contains more than product pages. List the checkout, shipping, payment, account and integration flows the business uses every day. Include subscriptions, bookings or custom product options where relevant. Record the extensions responsible for each flow so a migration review can focus on the actual store instead of assuming a standard installation.

Check product and customer data

Review a representative sample of products, variations, images, prices and stock. Check that customer accounts and order history are present in the new copy. A store may continue receiving changes during the migration. Agree how new orders, inventory updates and customer registrations will reach the new server before the final handover.

Test the complete checkout path

Use the payment provider’s test facilities when available. Add products, apply a valid coupon, select delivery and complete the order. Confirm taxes and shipping calculations match the intended store rules. Check failed or cancelled payments too. Avoid real charges simply to prove a page loads, and remove test orders from operational reports where appropriate.

Review caching and background work

Cart, checkout and account screens need visitor-specific behaviour. Confirm the cache setup does not serve one customer’s information to another. Check scheduled tasks and payment callbacks as part of the migration. If a provider callback or background job fails, the site can appear healthy while orders or stock updates stop progressing.

Verify email and external services

Place a test order and confirm the expected store emails are accepted by the mail provider and arrive at the intended addresses. Review shipping, accounting, CRM and inventory integrations as applicable. A working website does not prove that those external connections survived a change of server, hostname or network environment.

Plan the live handover

Choose a handover window appropriate for your order volume and agree who checks the result. A final data sync or short maintenance period may be needed. Monitor new orders and payment events after the switch, and keep access to the previous environment until the transition is verified. Send WebFulHost the store’s extension list and busiest trading periods when requesting a migration review.

Ask WebFulHost about your website or browse the knowledge base.

Use a short acceptance checklist

Before the switch, check a product, cart, account login, test-mode checkout, confirmation email and a scheduled task. Confirm that the private copy cannot accept real customer payments. Record expected results so the same workflow can be tested again after production DNS changes.

Assign the final order synchronisation

Decide who will account for orders and stock changes received after the first copy. Agree a cutover window with the business owner and payment provider where needed. An initial successful file transfer is not proof that the latest customer data is on the destination.

For the next steps, browse the hosting knowledgebase and compare current plan resources and billing terms.