A website migration moves website files, databases, and related services from one hosting environment to another. A migration can appear complete while old credentials, temporary accounts, copied configuration files, or access to the previous server remain active.
Table of Contents
Why security checks must continue after the move
Migration work often requires more access than normal website maintenance. People may create temporary administrator accounts, use SSH or FTP access, copy configuration files, or keep backups on the old host while the new environment is tested. These actions support the move, but they can leave additional ways into the website if they are not reviewed afterwards.
The old and new hosting environments should be treated as separate parts of the migration until the new site is working and the previous environment is no longer needed. Preparation helps reduce the risk of downtime and data loss, and it also gives you a clear point at which to review access and remove temporary migration items. See the preparation steps for moving a website to a new server.
Credentials and administrator accounts
One common mistake is leaving migration credentials active after the transfer. This can include hosting credentials, database credentials, administrator accounts, and temporary accounts created for a developer or migration task.
Review every account that was used during the migration:
- Remove temporary accounts that are no longer needed.
- Remove administrator access from accounts that do not need it after the move.
- Change credentials that were shared, copied, or used in more than one environment.
- Confirm that each remaining account has a clear purpose.
Do not assume that an account is safe to keep because it was created only for a short task. The relevant check is whether it is still required and whether its level of access matches its current purpose.
SSH and FTP access
SSH and FTP access can remain available on the old host even after the website is working on the new host. Access may also be left enabled on the new host with permissions that are broader than the migration requires.
Check access on both hosting environments. Remove unused access, review accounts created for the migration, and confirm which remaining users or services still need access. The review should cover both named accounts and any credentials stored for automated connections. Access to the old host deserves separate attention because it may still expose website files, databases, or backups.
File permissions and copied configuration files
Files copied during migration may keep permissions from the previous environment. A file or directory with excessive permissions can allow more users or processes to read or change it than intended. The same issue can affect configuration files copied for convenience during setup.
Review the permissions of the migrated website files and directories. Pay particular attention to configuration files, upload locations, backups, and files created during testing. Each item should allow only the access needed for the website and its required services. Remove copied files that are no longer part of the working site.
Configuration files may also contain connection details or other secrets. Check copied configuration files on the new host and the old host. Remove unused copies and make sure credentials that appeared in temporary files are no longer active.
Secrets, backups, and certificates
Migration can create several copies of sensitive data. These may include database connection details, application secrets, administrator credentials, backup archives, and certificate files. A copy that was useful during the transfer can become an overlooked access path afterwards.
- List the secrets used during the migration and identify where copies were placed.
- Remove temporary copies that are no longer needed.
- Change secrets that were exposed in copied files or shared during the move.
- Review backup archives on both hosts and remove obsolete copies according to your retention needs.
- Check certificates and related files on the active host, then remove unused copies from temporary locations and the old host.
Backups are part of the migration data set, not only a recovery task. They can contain the same website files, databases, and configuration details as the live site. Treat each backup as sensitive until it has been reviewed or removed.
Decommissioning the old hosting environment
Keeping the old host available can help with testing and rollback, but it also leaves another environment that requires access review. Before decommissioning it, confirm that the new site contains the required website files, databases, and related services. The migration process moves these elements from one hosting environment to another, so the old environment should not be removed until the new one is ready. Read about the migration process and continued access during the move.
After the new environment is confirmed, remove or disable unused accounts and access methods on the old host. Delete temporary migration files, copied configuration files, and obsolete backups. Check that the old host no longer serves the website or provides an unplanned route to its data. If the old environment must remain active, document why it remains available and include it in regular access reviews.
Final migration security check
- Review all administrator and hosting accounts on both environments.
- Remove temporary accounts and unused SSH or FTP access.
- Check file and directory permissions, especially for configuration files and backups.
- Find copied secrets and change credentials that were exposed during the move.
- Review certificates, backup archives, and temporary migration files.
- Confirm that the new host contains the required website data and services.
- Decommission the old host or keep it under the same access controls and review process.
A migration is not security-complete when the website first loads on the new host. It is complete when the required data and services are working, temporary access has been removed, copied sensitive files have been reviewed, and the old environment no longer provides unplanned access.