Migration failed or stuck
Blogger migrations run as background jobs. Most issues show up in Recent Migration Jobs on MigraSync → Blogger Migration or in the wizard progress panel.
Step 1 — Check job status
- Open MigraSync → Blogger Migration.
- Scroll to Recent Migration Jobs.
- Note status: running, completed, failed, or pending resume.
If a job is pending on the server, the wizard may show a resume banner — use Resume on the matching row or Scroll to Recent Jobs.
Takeout / local file path
| Problem | What to try |
| Upload fails or times out | See Takeout upload problems |
| “Invalid archive” or parse error | Re-export from Google Takeout; ensure Blogger is selected |
| Wrong blog in export | Export only the blog you need, or pick the correct blog after upload |
| __MACOSX or corrupt zip | Re-download export; upload ZIP without unzipping on Mac |
Guide: Migrate with Google Takeout.
Blogger API path
| Problem | What to try |
| Google sign-in popup blocked | Allow popups; retry — see Blogger OAuth issues |
| Blog not listed | Sign in with the Google account that owns the blog |
| Token expired mid-job | Re-authorize from the migration wizard and resume or restart |
Guide: Migrate with Blogger API.
Plan quota exceeded
If the wizard warns that your blog has more posts/pages than your plan allows:
- Upgrade at Pricing → Migration tab
- Or use Takeout if API quota was the bottleneck
See migration plans explained.
Host limits (memory / timeout)
Large blogs need adequate PHP resources:
- memory_limit 256M or higher recommended
- Long jobs use background processing — you do not need to keep the browser tab open
- If imports stop early, ask your host to raise max_execution_time for WP-Cron / Action Scheduler
Check system requirements.
Start fresh (careful)
To wipe WordPress and re-run a test migration:
- Purge content — irreversible; also clears SEO redirects
- Take a backup first if the site has anything worth keeping
Related
Related Articles
On this page