Recommended Free Tools
To migrate a website to Infomaniak, build the destination first, copy the site files and database, test the new copy, and only then change DNS or transfer the domain. WordPress sites can use archive-based plugins; other PHP, HTML, and database applications generally require an FTP file transfer plus a MySQL export and import. Email and domain registration are separate moves, and Infomaniak recommends handling web data, mail, and the domain in that order.
What you are actually migrating
A website move is usually several independent projects. Treating them separately makes it easier to test each part and avoid taking email or other services offline accidentally.
As an Amazon Associate I earn from qualifying purchases.
- Website files: HTML, PHP, images, themes, plugins, uploads, and other files in the current hosting account.
- Database: MySQL data used by WordPress, a CMS, an online store, forums, or another dynamic application. A static HTML site may have no database at all.
- Email: Mailboxes, messages, aliases, forwarding rules, and spam settings. Moving the website does not move mail automatically.
- Domain registration: The registrar account that controls renewal and transfer authorization. You can host the website at Infomaniak while leaving registration elsewhere.
- DNS: The records that direct web, mail, verification, and other services. DNS changes are separate from copying files.
Infomaniak’s external-transfer instructions require an eligible Web Hosting plan or Cloud Server and a blank website created on it before you start copying data. See Infomaniak’s transfer guide for the destination prerequisites.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallChoose the migration method
| Website type | Recommended route | What must be transferred |
|---|---|---|
| Static HTML/CSS/JavaScript | FTP or SFTP file copy | Site files; no database unless the site uses an external or custom data service |
| PHP application or non-WordPress CMS | Manual file and database migration | Files plus a MySQL export, then configuration changes for the new database |
| WordPress | All-in-One WP Migration or Duplicator | An archive containing the WordPress files and database, followed by URL and SSL checks |
| Website plus email and domain | Separate service moves in sequence | Web data first, mail data second, domain transfer last |
The WordPress workflow is documented in Infomaniak’s WordPress migration overview. Do not use a plugin archive for an application that the plugin does not support, and do not omit a database export merely because the visible site consists mostly of files.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Before you begin: make an inventory and backups
Record the current environment
- Identify the platform and version: WordPress, another CMS, a framework, or a static site.
- List every domain and subdomain, including staging names and API endpoints.
- Determine whether the application uses MySQL or another database, and note its size.
- Write down the current registrar, DNS provider, mail provider, and any third-party services that depend on DNS.
- Collect the old host’s FTP address, username, password, and connection port. Infomaniak’s generic instructions specifically require FTP credentials to retrieve the files.
- Save the current database name, server/host value, username, password, table prefix, and the export tool used by the old host.
Create recoverable backups
Download a complete copy of the old website and keep the SQL export outside the hosting account. Export a second database copy if the site is business-critical. Preserve the original configuration file until the new site has passed testing; it contains values you may need to compare, even though its old database credentials must not be reused blindly.
Lower DNS timing only if appropriate
If you control DNS and want a quicker cutover, you may lower the records’ TTL before changing them. The supplied Infomaniak instructions do not promise a universal propagation time or zero downtime, so plan for a transition period and keep the old site available until the new one is verified.
Build the Infomaniak destination
Create hosting and a blank website
Order or select an Infomaniak Web Hosting plan or Cloud Server, then add the destination website in Infomaniak Manager. The site should be blank before importing data; installing a second copy of an application into a directory containing unrelated files can create path and permission conflicts.
Create access and database resources
Create the FTP or SSH account that will receive the files and create a new database for the application. Record the database name, server address, username, and password displayed in Infomaniak Manager. These values are normally different from the old host’s credentials.
Use a preview address
Keep the temporary or preview address available while the production domain still points to the old host. This lets you inspect the new copy without changing public DNS. If the application redirects every request to the old domain, temporarily adjust its URL settings or follow Infomaniak’s preview troubleshooting guidance before testing.
Manual migration for HTML, PHP, and database-backed sites
1. Download the old files
Connect to the old host with an FTP client and download the complete document-root directory, including hidden files such as .htaccess when applicable. Confirm that uploads, media, generated assets, and any private configuration files required at runtime are included. Infomaniak’s general transfer procedure starts with retrieving the files through FTP.
2. Export the database
Open the old provider’s database-management interface, commonly phpMyAdmin, select the application database, and export it as SQL. Include the tables, structure, and data. A static site with no database does not need this step; verify the application’s own requirements rather than assuming that every site is database-free.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
3. Upload the files
Connect to the new Infomaniak site and upload the files into the document-root folder assigned to that website. Do not upload the local parent directory if it would create an extra level such as /public_html/site-name/ when the application expects its index file directly in the web root. Check that the expected index file is present at the root and that file permissions allow the web server to read it.
4. Import the SQL file
Open the new database’s management interface and import the SQL export. Large exports can exceed an interface upload limit; use the database tools available in your Infomaniak account or split the export according to the provider’s instructions rather than silently importing only part of it. Check for an error report and verify that the expected table count and row data are present.
5. Update the application configuration
Edit the application’s configuration file with the new database name, database server, username, and password shown in Infomaniak Manager. Keep the table prefix and any application-specific salts or keys unless the software’s migration documentation says otherwise. For a PHP application, also check its required PHP version, writable cache or upload directories, scheduled tasks, and path settings.
6. Test the preview copy
Open the preview address and test representative pages, images, forms, logins, search, uploads, database-backed features, and any payment or API integrations in a safe mode. Inspect server and application logs for PHP errors, missing extensions, permission failures, and database connection errors. Do not direct production traffic to the new host until these checks pass.
Free tools Windows power users keep installed
One-click scans. No signup required.
WordPress migration with an archive
Infomaniak documents two plugin-based approaches: All-in-One WP Migration and Duplicator. The exact screens can vary by plugin version, so follow the current plugin prompts while preserving the sequence below.
All-in-One WP Migration procedure
- On the old site, install and activate All-in-One WP Migration.
- Use the plugin’s export function to create an archive of the WordPress site, then download that archive to your computer.
- On the new Infomaniak hosting, create a fresh WordPress installation at the destination site.
- Install and activate the same migration plugin on the new installation.
- Use the import function to upload the archive and confirm the replacement operation when prompted.
- After the import, sign in again with the credentials contained in the migrated site, not necessarily the temporary credentials created for the blank installation.
- Check the site address and WordPress address, then save the permalink settings so rewrite rules are regenerated.
- Configure the SSL certificate when the domain is ready and use the HTTPS address. Mixed-content warnings may require updating hard-coded HTTP URLs in content or themes.
Infomaniak’s detailed instructions are at the All-in-One WP Migration guide. If the archive exceeds the configured server-side import limit, increase the maximum permitted import size in the site settings or use a migration method that can handle the archive size. Do not assume that a browser upload succeeded merely because it reached 100 percent; confirm that the plugin reports a completed import.
Duplicator route
Duplicator packages the WordPress files and database and provides an installer workflow. Generate the package on the old host, upload the package and installer to the new site, run the installer against the new database, and complete the URL and administrator checks it requests. Use one method for a given migration rather than importing an All-in-One archive and a Duplicator package over one another.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
WordPress checks after import
- Open the home page, several posts, category and search pages, and a URL that contains an image or downloadable file.
- Test administrator login, media uploads, forms, comments if enabled, cron-driven tasks, and plugin settings.
- Verify that the site address uses the intended domain and HTTPS scheme after the certificate is active.
- Regenerate permalinks and clear page, object, and CDN caches only after confirming the migrated files are present.
- Check redirects carefully when viewing the preview address; a forced redirect to the production domain can make the new copy appear unreachable.
Move email and the domain in the safe order
If the move includes web hosting, mail, and domain registration, Infomaniak’s official order is designed to reduce interruption and data loss: “migrate your services in the order indicated.” The sequence is web data first, mail data second, and the domain last. Read the complete service-transfer guide for the provider’s current process.
Web data first
Complete the file and database migration and verify the preview copy while the old domain still reaches the old site. This establishes a working destination before DNS or registration changes.
Mail data second
Create the Infomaniak mailboxes and copy messages before changing MX records. Recreate aliases, forwarding, autoresponders, and any application SMTP credentials. Keep the old mail service available during propagation and check both sending and receiving from addresses outside your domain.
Domain transfer last
A domain transfer is not required to host the website at Infomaniak. If you do transfer registration, Infomaniak’s domain guidance says the domain should have been registered or transferred at least 60 days before starting the transfer, the owner-profile email must be valid, and the current registrar supplies the transfer authorization code, also called EPP, AuthCode, or AuthInfo. See Infomaniak’s domain-transfer requirements.
Preserve DNS records before changing nameservers
Before a domain transfer or DNS change, export or copy every existing record. At minimum, record the A, MX, TXT, and CNAME records. Include records used for email authentication, domain verification, subdomains, APIs, analytics, and services that will remain at the old provider.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsIf any service stays elsewhere, retain the current DNS settings for that service. For example, pointing the website’s A record to Infomaniak does not mean you should replace MX records that still deliver mail to another provider. The correct DNS arrangement depends on which service is hosted where; moving a website alone does not require moving the registrar or all nameservers.
| Record | Typical purpose during migration | What to verify |
|---|---|---|
| A/AAAA | Directs a hostname to a web server | Use the new destination value only for hostnames moving to Infomaniak |
| MX | Directs incoming email | Keep old mail targets until mailboxes and copied messages are ready |
| TXT | SPF, DKIM, DMARC, verification, and policy data | Recreate every record needed by mail and external services |
| CNAME | Aliases subdomains or service endpoints | Preserve aliases for services that remain outside Infomaniak |
Cut over and validate production
- Freeze or document content changes on the old site so edits made during copying are not lost.
- Perform a final file and database synchronization if the site changed after the initial backup.
- Confirm the new copy works through its preview address and that certificates, redirects, and application URLs are ready.
- Change only the DNS records required for the services moving to Infomaniak, or update nameservers if that is your chosen DNS arrangement.
- Monitor the old and new endpoints while DNS caches expire. Keep the old hosting account and mail service active until traffic and messages are arriving correctly at the destination.
- After propagation, test the live domain from more than one network and device, then recheck forms, logins, uploads, email delivery, and third-party callbacks.
Infomaniak’s internal hosting-migration guidance recommends testing a preview copy before going live and describes a 30-day test-and-adapt period for a specific migration from an existing Infomaniak Web Hosting service to its current hosting offer. That 30-day period is not a standard promise for a move from another provider. See the internal migration guidance for its limited scope.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Troubleshooting common migration failures
The site shows a database connection error
Recheck the database name, server, username, and password in the application configuration. Confirm that the SQL import completed and that the user has permission to access the new database. A correct file upload cannot compensate for an incomplete or misnamed database.
The preview redirects to the old domain
WordPress and many CMSs store the canonical URL. Review the site URL settings and redirect rules, temporarily disable forced redirects that block preview testing, and restore the intended HTTPS redirects after the domain points to Infomaniak.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Images or pages return 404 errors
Check that uploads and rewrite files were copied, that the document root is correct, and that permalink or rewrite rules were regenerated. Case-sensitive filenames can also fail after a move between servers.
The WordPress archive will not import
Check the server-side maximum import size and available disk space. Increase the permitted limit when possible, or use Duplicator or another supported method for an archive that exceeds the limit. Verify the plugin’s completion message and inspect the destination rather than relying on the browser progress bar.
Email stopped after the DNS change
Compare the live MX records with the records you saved before migration. Recreate missing TXT records used by SPF, DKIM, or DMARC, confirm that the destination mailboxes exist, and keep the old service available while cached DNS records expire.
Final migration checklist
- Destination hosting and a blank website exist at Infomaniak.
- Old files and a complete database export are stored safely.
- FTP/SSH credentials and new database credentials are recorded.
- All required files are uploaded to the correct document root.
- SQL data imports without errors, and the application configuration uses the new database values.
- WordPress archives, if used, finish importing and the site URL is correct.
- Preview testing covers pages, media, forms, logins, uploads, and application-specific features.
- Existing A, MX, TXT, and CNAME records are saved, especially for services remaining elsewhere.
- Mailboxes and message copies are ready before MX or domain changes.
- DNS is changed only after the new site is verified, and the old services remain available during propagation.
Sources and current requirements
Instructions and requirements can change as Infomaniak updates its Manager interface and hosting products. The provider’s current references for this process are:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
- Transfer Web Data to Infomaniak (updated 10 June 2026).
- Migrate a WordPress site to Infomaniak.
- Migrate a WordPress site using All-in-One WP Migration (updated 22 May 2026).
- Transfer all your external services to Infomaniak (updated 28 April 2026).
- Transfer your domain name to Infomaniak.
- Transfer a website from one Infomaniak hosting to another.
- Migration: keep the current content of your hosting (updated 28 April 2026).
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
