Thank you for the question and for using Prime Mover! The best strategy is to always test your site before you roll out to your new server with better specs. This is to make sure that your current site functionality will still work with the new server.
There are several things to test in this case including:
- Visual testing (how the site looks – design related)
- Functionality – the site unique features
- Plugins compatibility (e.g. you might be using plugin that is not compatible with newer PHP version ,etc.)
- Themes compatibility (e.g. your theme might not work with newer PHP version).
- Database compatibility – you might be using custom functionality that still depends access on older database version.
In this case – it would be best to test it in an environment similar to your new server (e.g. same PHP version, same server (e.g. Apache, Nginx), same OS (e.g. Linux or Windows server), same MySQL version, etc.).
You can do all this test in your local environment if you can have it. It is always better to test locally so you can easily debug things just in case something is not working.
Full local testing before moving to new production server will give you an idea of your site compatibility with the new server. Once you see that your site fully works in that new server specs. This is the only time to move to production.
You can use Prime Mover to do all the site migrations (e.g. from your current server to local server, current server to new server ,etc.). You can also use Prime Mover to backup things first before you test (e.g. update plugins ,or do some experiments, etc.)
