GICT knowledge base
GreenGeeks to InterServer: Website Migration Guide
Published
This guide covers moving a website from GreenGeeks to an InterServer service. First confirm the destination product, domain, application, database and email scope. A website-file copy alone is not a complete migration.
Complimentary migration eligibility: InterServer provides migrations for web hosting plans only, limited to cPanel-to-cPanel and DirectAdmin-to-DirectAdmin. VPS and dedicated-server migrations are not offered. Cross-panel transfers and website-builder conversions are outside this service; the manual instructions below are for self-managed moves when the matching-panel web hosting requirements are not met.
GreenGeeks currently documents cPanel account backups for accounts under 10 GB. For larger accounts, its instructions call for a manual files-and-database backup or a provider-generated full backup, which may incur a fee. Generated cPanel backups are removed after 48 hours, so download them promptly and do not treat provider disaster-recovery copies as your own export.
Export the website files
Sign in to the GreenGeeks dashboard over HTTPS and open cPanel for the correct hosting account. If the account-backup feature is available, open Files > Backup, request a full account backup, and download the completed archive through authenticated access. Confirm with the destination provider that it can restore this format.
For a site-specific transfer, download the site’s document-root files using the authenticated File Manager, SFTP or FTPS where enabled. Include hidden files such as .htaccess and required data outside the document root. Do not place an archive in a public document root to make it downloadable.
Export its database
If the application uses MySQL or MariaDB, identify the database and credentials from its configuration. In cPanel, open phpMyAdmin, select the correct database, choose Export, and save an SQL dump locally. For a large database, use an appropriate command-line export or ask the provider for a supported method. Protect the dump because it can contain account and customer data.
Transfer and test at InterServer
Upload the files and database dump using a private authenticated method. Create or request the destination database, import the dump, and update the application configuration with the destination credentials. Confirm the correct destination restore method before uploading a full cPanel account archive: a full archive is not restored by an ordinary account-level cPanel user.
Preview the site before changing DNS. Test application login, database-backed pages, forms and any required scheduled tasks. Move mailboxes and DNS records separately if they are in scope. Keep the source service available until the destination is verified. See the cPanel migration guide for account-backup options and the migration backup checklist for pre-cutover checks.
For help restoring at InterServer, open a ticket through the customer portal and follow the migration support process. Include the source panel, destination service, domains and whether mail is moving. Arrange private backup delivery with support.
Follow GreenGeeks’ current website-backup instructions and backup policy for your plan’s availability and charges.
Related guides
Check MariaDB Versions and Compatibility on Shared Hosting
Check your actual MariaDB/MySQL server version, maintenance coverage and application requirements before requesting a shared-hosting upgrade or move.
MigrationMigrate WordPress with Migrate Guru: Scope and Safety Checks
Use Migrate Guru for a scoped WordPress copy. Review third-party processing, protect the destination and verify the application before changing DNS.
MigrationcPanel to DirectAdmin: Conversion, Restore and Verification
Convert a supported cPanel account archive to DirectAdmin with private delivery, ownership mapping and application/mail checks before DNS cutover.
MigrationcPanel to CWP: Private Backup Import and Recovery Checks
Plan a self-managed cPanel-to-CWP import. Transfer backups privately, check account conflicts and verify websites, mail and DNS before cutover.
