IONOS (1&1) to InterServer: Self-Managed Website Transfer

This guide covers moving an IONOS website, including an older 1&1 hosting account, to InterServer. First identify the product: web hosting, a managed WordPress installation, a website builder and a VPS expose different data and export tools.

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.

Export files and the database from web hosting

Find the source site’s installation directory and database name in the application configuration. For IONOS Click & Build installations, the application tile’s Technical data identifies both; see IONOS Click & Build export guidance.

1. Obtain the source package’s connection details from IONOS. Use SFTP for Linux hosting where supported, or the documented FTPS connection for Windows hosting. Follow the IONOS connection guide.
2. Download the installation directory, hidden files and other required application data. In FileZilla, the remote server is on the right and the local destination on the left; downloading copies remote files to your computer. Check failed transfers.
3. Open phpMyAdmin for the matching database, select it and use Export to save an SQL copy containing the needed structure and data. Repeat for every database the application uses.

IONOS documents SFTP downloads and MySQL/MariaDB exports. A file download and SQL dump form a manual application export, not a full cPanel account backup. Keep them private and out of public web directories.

WordPress, builders and server products

For WordPress, preserve the database, uploads, themes, plugins and application configuration using the access permitted by your plan. WordPress’s Tools > Export creates a content XML file; it is not a complete installation backup. IONOS’ WordPress export guide explains the available methods. A restore button that rolls back the source site is not a migration export and can overwrite newer work.

For MyWebsite builder products, IONOS states that the builder project cannot run outside its infrastructure. Check its builder export limitations and plan a rebuild where needed. A VPS additionally requires a plan for its web server, runtimes, scheduled jobs and other services; do not assume the shared-hosting procedure recreates them.

Restore and cut over

Confirm the destination application and database versions, restore into an isolated destination and update connection settings. Preview the site using its real hostname, test its important workflows and plan a final data synchronization before changing DNS. Preserve existing mail records when mail remains elsewhere, and retain the source service until verification is complete.

Use the InterServer customer portal for questions about your destination hosting settings. IONOS-panel, builder and VPS transfers described here are self-managed; they are outside InterServer’s matching-panel web hosting migration service.