Move a Former Media Temple Website to InterServer

If your website was hosted at Media Temple, first locate the account and product that now hosts it. GoDaddy’s February 2023 announcement described moving Media Temple customers to GoDaddy infrastructure and sunsetting the brand. The historic Grid and AccountCenter screens are no longer a dependable universal export procedure.

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.

Identify the current source service

Sign in to the provider account you currently use and match the website to its hosting product. Domain registration alone does not establish where the website or email is hosted. If the former Media Temple account or data is missing, ask the source provider to identify the current service and available backups before cancelling anything.

• Web Hosting with cPanel: use that product’s account-backup or manual-export controls. The cPanel migration guide covers supported account archives and GoDaddy export differences.
• Managed WordPress: export the website’s files and database through the access supplied for that product. GoDaddy’s manual WordPress migration guide distinguishes application files, database exports and destination configuration. Do not expect a full cPanel archive from a product that does not use cPanel.
• VPS or another server product: inventory the installed panel, runtime, databases, mail services and scheduled jobs. Arrange a compatible server or application migration rather than applying old Grid instructions.

Keep a complete, private export

For an application migration, download the necessary files using authenticated HTTPS, SFTP or FTPS where available. Include hidden configuration and data outside the public site directory. Export each required database with structure and data; a directory archive does not capture a live database.

Keep the export outside public web directories. Import databases into the intended destination and protect any existing destination data. SQL dumps containing DROP statements can remove tables during import; do not use them to merge into an unrelated live database.

Handle email separately

Check whether the domain’s mail is still on hosting, uses a separate GoDaddy mail product or has moved to Microsoft 365. A website backup does not transfer a Microsoft 365 mailbox. Preserve current MX, SPF, DKIM and other required mail records unless mail is intentionally moving. Agree a mailbox migration and recovery plan separately.

Test at InterServer before changing DNS

Confirm the destination product, update application credentials and preview using the site’s real hostname. Test database-backed pages, login, forms and necessary jobs while preventing duplicate emails or payments from a test copy. Reconcile new writes before cutover and retain the source until the new site is verified.

Open a ticket in the InterServer customer portal with the current source product, destination service, domains and mail scope. Use the migration support process to confirm eligibility and private export delivery.