Important: This synchronization must be performed immediately before the DNS cutover. Do not perform this step if you are not ready to update your DNS records within a short window of time.
Before you begin
You will need:
Access to your current hosting provider's control panel or file manager.
Access to the Hostek migration environment or control panel.
A list of the specific database names and usernames for your website.
A stable internet connection to transfer the final data.
Perform the final file synchronization
Log in to your current hosting provider's control panel.
Use an FTP client or the provided File Manager to identify all files associated with your website.
Upload the final set of files to the designated directory on the Hostek server.
If you are using a migration tool, run the final "Sync" or "Update" command to pull the latest files from the source to the destination.
Perform the final database synchronization
Log in to your current hosting provider's database management tool (such as phpMyAdmin).
Export the database as a
.sqlor.sql.gzfile.Log in to the Hostek management interface.
Access the database management tool for your migrated site.
Import the
.sqlfile into the Hostek database.Verify that the number of tables and the size of the database match the source.
Confirm the result
The file count on the Hostek server matches the count on your original host.
The database on the Hostek server contains the most recent entries, including any content added since the initial migration.
The website is accessible on the Hostek server (via a temporary URL or IP address) and displays the correct content.
If the database import fails due to size
If the database is too large to import via a web-based tool like phpMyAdmin, use a command-line tool or a migration script to import the .sql file directly into the Hostek database.
Limitations
This procedure does not include the process of updating DNS records. You must perform the DNS cutover only after this synchronization is confirmed successful. This process also does not include the update of application-specific configuration files (such as wp-config.php or .env files) to point to the new database credentials.
