What gets migrated
- Full database — posts, pages, users, options, custom tables
- Uploads folder (
wp-content/uploads/) - Active theme and all plugins
- Must-use plugins (
mu-plugins/) - Custom directories you add to the include list
Exporting a site
- On the source site, go to Wigmorean → Super Migrator → Export
- Choose what to include (Full Site is the default)
- Click Start Export
- The migrator streams the archive in chunks and avoids PHP memory limits by working in 20 MB windows
- When done, download the
.wigmigfile — this is a portable, compressed archive
Archive size. The archive is compressed, but for sites over 2 GB, export directly to S3 (configure in Settings) — the download link stays as a short-lived signed URL.
Importing on a fresh site
- Install Wigmorean Super Migrator on the destination site
- Go to Wigmorean → Super Migrator → Import
- Upload the
.wigmigfile (or paste the S3 URL) - Click Analyze — the migrator extracts and previews the archive
- Review the data mapping (see below)
- Click Import
Data mapping
Before import runs, you'll see the data mapping step. This is where you tell the migrator:
- The old site URL and the new site URL — so it can rewrite every hardcoded link in posts, options, and serialized data
- Which user accounts to merge, skip, or renumber (if the destination has existing users)
- Which table prefix to use (if different from source)
The search-and-replace is serialization-aware — it walks meta_value fields that contain serialized arrays and rewrites URLs inside them without breaking the structure.
Post-import checklist
- Log in to the new site (admin credentials come from the archive)
- Go to Settings → Permalinks and click Save Changes to flush rewrite rules
- Test a few pages, images, and forms
- Reconfigure third-party services with the new domain (Stripe webhook, SMTP sender, analytics)