Importing a site creates an isolated CanaryWP testing environment from a WordPress backup archive.
Supported sources
CanaryWP’s import pipeline supports common WordPress backup archive formats, including:
.wpress.zip- Supported tar-based archives
The archive must contain a structure the CanaryWP restore pipeline can recognize.
Current upload limit
The current import documentation defines an upload limit of 700 MB.
If an archive exceeds the allowed size, reduce the backup where appropriate or use another supported migration approach provided by your organization.
Before importing
Check that:
- You selected the correct archive.
- The backup completed successfully.
- The archive belongs to the intended source site.
- You know which environment you are creating.
- You have credentials if WP Admin testing will be required.
Avoid uploading archives merely because their filenames look correct. Confirm the source whenever possible.
Import a site
1. Open Import Site
Start a new site import from CanaryWP.
2. Select the archive
Choose the WordPress backup you want to restore.
3. Review source information
Confirm the source site identity.
This is particularly important when you manage multiple sites with similar names.
4. Review destination settings
Check the CanaryWP destination details that are presented, including applicable:
URL
Region
Plan
Environment information
Login information
5. Start the import
CanaryWP processes the archive and prepares the destination.
The exact restore steps depend on the archive, but the process can include:
Upload
Archive preparation
File restore
Database import
URL rewriting
WordPress preparation
Runtime startup
Verification
While an import is running
Do not treat the environment as ready merely because a URL has been assigned.
Wait until the workflow reports that the instance is available.
If an import fails, keep the original archive until the cause has been investigated.
After the import
Verify the site manually before beginning maintenance.
Check:
- Homepage
- Important landing pages
- Navigation
- Images and other media
- WP Admin
- Plugin list
- Theme
- WordPress version
- PHP version
- Site Health
Then run Site Testing.
URL differences
The CanaryWP environment normally uses a different URL from the source site.
Seeing the CanaryWP URL inside the imported environment can therefore be expected after the restore process has rewritten site URLs.
Common import problems
Archive rejected
Confirm the archive format and size.
Import cannot determine site structure
The backup may not use a layout supported by the restore pipeline.
Site imports but pages redirect to production
Review site URL configuration, redirects, plugins, and database values.
Images or assets are missing
Check whether those files were included in the source backup and whether the imported URLs were rewritten correctly.
WP Admin does not open
Confirm credentials and inspect logs for WordPress or PHP errors.
Site displays a fatal error after import
Review PHP compatibility, plugins, theme code, and logs before changing the environment.
Recommended next step
Create a baseline Site Testing run before changing the imported site.