We're very sorry to see you go, but we'll make the transition as easy as possible! Please try to make sure you and your new host read this document and have a good migration plan in place.
In normal production, your files are not stored in one place. The database, web server and media server are all in different locations. We normally need at least a day's notice to prepare your site for migration.
Performance Foundry does not store WordPress files in a publicly accessible folder. Your host will need to have a 'blank' WordPress instance to add your content files to. Copying the symlinks we use to your new host will not work.
Performance Foundry can be hired to migrate your site away; or there are three major strategies people use for DIY migrations:
Alternatively, if your host would like access to the files and WordPress install, we can arrange that. We do not have cPanel or other GUI. Your server is controlled from the command line, reducing security and performance impacts.
You can add your new host as an admin user from within the WordPress dashboard (User > Add New).
Your new host can send you a "public key", and you can pass that onto us. We will create an sFTP user for them, so they can access the files through sFTP. We do not have password-based sFTP access.
Most migration plugins work perfectly with our systems. Please be sure we have already moved your files from the media server, and that you avoid banned plugins.
We do not handle redirects through the WordPress app. Redirects will need to be created by your new host.
Other premium services, such as Thumbor and ElasticSearch will not work from outside our hosting environment. Please ensure your new host knows what they're doing, and a proper migration plan is in place.
Performance Foundry runs two sets of MU Plugins across all our hosted sites. One gives you the Foundry Anvil plugin and has several controls for performance and security. The other is a suite of tools from Pagely, designed to assist with integration into the hosting stack, including performance, security, CDN and caching tools.
We strongly recommend you do not migrate these plugins to your new host, and that you find replacements for their functions. Your new host should be able to help you choose the best security, caching, CDN and performance-enhancing functions for their environment.