The staging, server setup, DNS and testing behind a smooth website migration
When people hear that a website is moving from Cloudways to RunCloud, they may think the process involves copying the website, changing a few settings and waiting for it to load.
In reality, a website migration involves much more than moving files.
A website can contain important pages, images, forms, plugins, tracking codes and years of business content. If the migration is rushed, a contact form may stop working, images may disappear, SSL may not load correctly or the website may become temporarily unavailable.
In my role with Opdee, I prepare and manage this process. This includes creating staging sites, preparing servers, configuring the new environment, updating DNS and testing the website before and after the migration.
The goal is not only to move the website but make sure it continues working properly for visitors and the business.
Why Move from Cloudways to RunCloud?
The setup we use combines Vultr cloud servers with RunCloud server management.
Vultr provides the cloud server where the website runs. RunCloud gives the technical team a central dashboard for configuring and managing that server.
Cloudways provides managed hosting through one platform. With Vultr and RunCloud, the cloud server and server management are handled separately. This gives the technical team more visibility and control over the website environment.
With a Vultr server managed through RunCloud, we can:
- Configure the server around the website’s requirements
- Select suitable server resources and locations
- Create staging environments
- Manage WordPress websites and applications
- Configure caching and performance settings
- Use Redis for object and database caching where appropriate
- Manage domains and DNS settings
- Install and maintain SSL certificates
- Apply server-level security settings
- Monitor server health and resource usage
- Give developers controlled access
- Manage several client websites through a consistent process
For clients, this means a more organised approach to staging, deployment, maintenance and website support.
The benefit is not simply changing the hosting platform. It is placing the website in a server environment that can be managed around its needs.
Creating a Staging Site
Before creating the staging site, the existing website is reviewed to identify its important pages, content, forms, plugins and tracking systems. This helps ensure that nothing essential is missed during the migration.
A staging site is a temporary version of the website used for development, configuration and testing. It allows the team to work on the new environment without making changes directly to the live website.
This gives developers a safe place to build and test the website before it is connected to the client’s real domain.
Making changes directly to a live site introduces serious risk, as a minor error can break forms, layouts, or performance in front of customers. A dedicated staging environment ensures every update is safely tested and resolved before going live.
Preparing the New Server
Once the staging environment has been created, the new server needs to be prepared.
The server must be ready for the website’s current needs and future maintenance.
A website should not only load on the new server. It should also have the settings needed to support security, performance and regular updates.
Moving the Website
After the new environment is prepared, the website can be transferred from Cloudways.
Before the transfer, we verify that the website has a current backup and that the migration plan is clear.
After the transfer, we compare the staging website with the original version, checking that the content is present, the pages load correctly and the website behaves as expected.
Testing Before the Domain Change
Before connecting the client’s real domain, we test the website on staging across desktop, tablet and mobile devices.
We also use browser testing tools such as Sizzy to review the website at different screen sizes.
The testing process includes checking:
- Page layouts
- Mobile responsiveness
- Navigation menus
- Internal links
- Images and media
- Call-to-action buttons
- Contact forms
- Email links
- Click-to-call phone numbers
- Booking systems
- Interactive website features
A website may look fine on a desktop computer but have problems on mobile. A button may be difficult to press, a section may overlap another part of the page or a form may fail to send an enquiry.
Visual and functional testing are both necessary, this is known as QA testing and is imperative for a successful transfer or website launch.
Testing Contact Forms
Contact forms need more than a visual check because they are often responsible for receiving new business enquiries.
We send a test submission and check whether:
- the form accepts the information
- the correct email address is used
- the enquiry arrives
- the confirmation message appears
- the form works on mobile
- the security settings affect delivery
A website can look correct while silently failing to deliver enquiries. If a potential customer submits a form and the business does not receive it, the website is not performing its main function.
Updating DNS and SSL
Once the staging website has passed testing, the client’s domain can be connected to the new server.
This requires updating the DNS records so the domain points to the new environment.
DNS changes can take time to propagate. During this period, some visitors may still reach the previous server while others begin reaching the new one.
We check that:
- The DNS records point to the correct server
- The domain loads correctly
- The SSL certificate is active
- The website uses HTTPS
- The correct website appears at the domain
- Important pages remain accessible
- Forms and key features continue working
An incorrect DNS record can stop the website from loading, while an SSL issue can create a security warning for visitors.
Checking the Live Website
The migration is not finished when the domain starts loading.
After the DNS change, we test the live website again because the live environment may behave differently from staging.
We check:
- The homepage and key landing pages
- Navigation and menus
- Links and buttons
- Images and content
- Contact forms
- Phone and email links
- Mobile responsiveness
- Website speed
- Plugins and interactive features
- SSL and HTTPS
We also check the caching settings. Old cached files can cause visitors to see an earlier version of the website or prevent recent changes from appearing.
The important question is not only: Is the website online?
It is: Can visitors use the website properly?
A Successful Migration Should Feel Invisible
For visitors, the ideal migration is one they never notice.
They should be able to visit the website, browse its pages, submit an enquiry and use its features without interruption.
Behind that experience is a process involving:
- Website review
- Staging
- Server preparation
- Website migration
- DNS updates
- SSL configuration
- Functional testing
- Performance checks
- Post-launch quality assurance
A website is not successfully migrated just because it is online.
It is successfully migrated when it is secure, functional, fast and ready for customers.
What Happens After the Migration?
After launching, we carry out another quality assurance check across desktop, tablet and mobile devices. We also check that the website’s tracking systems are recording information correctly.
This may include checking or setting up:
- Google Analytics
- Google Tag Manager
- Google Search Console
- Bing Webmaster Tools
- Clarity
- Conversion and key-event tracking
After any migration or launch, Opdee provides 45 days of server maintenance at no additional charge. During this period, we monitor the server and check that the website continues to run properly.
After the complimentary month, ongoing maintenance is optional, however maintenance helps keep the website secure, functional and ready for visitors.
If you are planning to move your website from Cloudways to a Vultr server managed through RunCloud feel free to contact Opdee to discuss your requirements.
Our core belief is simple: websites must perform, not just exist.
