Prepare and test your Agiler project before switching your existing domain. Keep the original site available until the new site is working and you have accounted for any content created during the move.

Choose what to move

For a blog or site whose design you plan to rebuild, WordPress’s content export and import tools provide a straightforward starting point. They transfer content such as posts, pages, and comments; they do not copy installed themes, plugins, the full database, or the complete site configuration. See the WordPress export and import guide.

For a complete copy, including plugin settings, customer accounts, or shop orders, plan a files-and-database migration. Contact us before starting if you need help choosing a method, have a large database, or are moving a multisite network. Include your current host, approximate file and database sizes, WordPress and PHP versions, and whether the domain will change. Do not include passwords or database dumps in your initial message.

Prepare the destination

  1. Back up the source site’s files and database and keep a copy you can recover independently of the old host. Both are needed for a full-site backup; see WordPress backup guidance.
  2. Create an Agiler project and choose a PHP runtime compatible with your themes and plugins. You need the Admin or Developer workspace role to create and manage the project.
  3. Complete WordPress setup on the assigned agiler.cloud domain. Use this address for initial testing while the existing domain continues to serve the source site.
  4. Record integrations you will need to configure, such as email delivery, payment providers, webhooks, and scheduled tasks. Use test settings where available so the copy does not send customer messages or process live transactions during testing.

Import WordPress content

Use this workflow when moving content into a fresh WordPress installation:

  1. In the source WordPress admin, open Tools → Export, choose All content, and download the export file.
  2. On the Agiler site’s WordPress admin, install the themes and plugins the content needs, including plugins that define custom content types.
  3. Open Tools → Import. Under WordPress, choose Install Now, then Run Importer.
  4. Upload the exported XML file, map its authors to the appropriate users, and select Download and import file attachments if you want the importer to fetch media. Keep the source site and its media URLs accessible while this runs.
  5. Review the import results and check posts, pages, comments, and media. Recreate site settings and check the entire media library; a content export is not a complete file backup.

The WordPress importer documentation explains the importer options. If an import fails, inspect what was already imported before retrying to avoid duplicate content.

Moving the complete installation

Agiler provides a Files page for file and folder uploads and WP-CLI access through the Agiler CLI. These tools can support a migration, but copying files alone does not transfer database content. Check the requirements of your chosen migration method before using it on the destination.

Preserve Agiler’s generated wp-config.php. It obtains database connection details from the project runtime and supplies site URL defaults. Replacing it with your old host’s configuration can break the destination. Have any custom constants and database table prefix reconciled with the imported database as part of the migration.

Do not leave SQL dumps or migration archives in the public site files. If your migration needs a database import, URL replacements, or a plugin-specific restore procedure you have not tested on Agiler, contact us to plan that step before changing DNS.

Test and switch traffic

Check the destination’s home page, representative posts, navigation, images, downloads, and WordPress login. Test forms, search, email delivery, and any checkout or membership flows using appropriate test accounts. Check that links and embedded media point to the intended site; changing the domain does not necessarily update URLs stored in content or plugin settings.

For a site that receives orders, comments, registrations, or frequent edits, schedule a final synchronization and pause new writes on the source during that window. Otherwise, changes made after your initial copy will be missing from Agiler.

When the copy is ready:

  1. Create an Agiler backup and wait for it to complete.
  2. Follow Connect a custom domain to add the domain, update its DNS records, and check its HTTPS status. Preserve unrelated records, such as those used for email.
  3. Set the intended domain as Site Domain, then recheck the public site, login, links, and integrations on that domain.
  4. Configure automatic backups and review the launch checklist.

Keep the old hosting and source backup until DNS has propagated and you have verified the migrated site. If you need to switch traffic back, account for any new data written to Agiler first so that orders, submissions, or edits are not lost.