MigraSync Documentation

Everything you need to set up, connect, migrate, backup, and restore your WordPress websites with MigraSync SaaS and the MigraSync Plugin.

Step-by-step guides: Knowledgebase · Need help? Help Center

System requirements

MigraSync SaaS connects to your WordPress site through the MigraSync Plugin. Your server must meet the minimum requirements below before you purchase or connect a paid plan. After installing the plugin, open MigraSync → General and review the System Requirements panel for a live Pass / Fail checklist.

Required (plugin will not run without these)

  • PHP 8.1 or newer
  • WordPress 6.2 or newer
  • OpenSSL PHP extension (AES-256-GCM encryption)
  • JSON PHP extension
  • HTTPS outbound access to migrasync.com

Recommended (plugin runs; some features may be limited)

  • cURL extension — large cloud uploads
  • ZIP extension — Google Takeout .zip imports
  • PHP memory_limit 256M or higher — large backups and migrations (unlimited / -1 is fine)

Hosting compatibility is your responsibility. If your server does not meet these requirements and you have not substantially used a paid plan, you may qualify for a refund under our Refund & Cancellation Policy within 14 days of purchase.

1. Installing the MigraSync Plugin

MigraSync has two parts: MigraSync SaaS (account, billing, API key on migrasync.com) and the MigraSync Plugin (runs on your WordPress site). Download the plugin from My Dashboard, upload it once per site, then connect your API key.

Installation Checklist

  1. Sign in at migrasync.com and open My Dashboard.
  2. Download the MigraSync Plugin (.zip) from Overview or API Key.
  3. In WordPress admin, go to Plugins → Add New → Upload Plugin.
  4. Select the ZIP file, click Install Now, then Activate.
  5. A MigraSync menu appears in the admin sidebar (General, Blogger Migration, WP Backup, WP Restore, and more).

Detailed guide: Install MigraSync Plugin

2. API Key Authentication & Connection

Your WordPress site connects to MigraSync SaaS with a unique API key. The key syncs your plan entitlements (migration package, backup subscription) and authorizes secure communication between your site and migrasync.com.

How to connect your site

Copy your API key from My Dashboard → API Key. In WordPress, open MigraSync → General, paste the key into the API Connection field, and click Save & validate. When connected, pillar cards unlock for Migration, WP Backup, and WP Restore based on your active plans.

Rotating your API key

If you regenerate your key in My Dashboard, the old key stops working immediately. Update every WordPress site that uses MigraSync with the new key. Finish running migration or backup jobs before rotating.

3. Running Blogger-to-WordPress Migrations

Import posts, pages, comments, and images from Google Blogger into WordPress. MigraSync supports two import paths — Google Takeout (local file) and Google Blogger API (sign-in) — with the same wizard steps for options, consent, and progress tracking.

1. Google Takeout (local file)

Open MigraSync → Blogger Migration and choose Local file (Google Takeout). Upload a .zip, .tgz, .atom, or .xml export. Best for large blogs and avoiding Google API quotas.

2. Google Blogger API

Choose Google Blogger API, then Connect Blogger account to sign in with Google via MigraSync SaaS. Select your blog from the list — fastest setup for small to medium sites within plan quotas.

3. Import options & progress

Configure images, comments, categories, drafts, and author handling. Start migration and track progress in the wizard and Recent Migration Jobs. Large jobs continue in the background.

4. Free migration trial

The free migration trial imports a limited preview (posts and pages) so you can test quality before buying Starter or Standard. Upgrade to remove limits and migrate your full archive.

After migration, generate live 301 redirects from captured Blogger URLs — see SEO 301 Redirects below.

4. WP Backup

WP Backup creates encrypted copies in MigraSync Managed Cloud. Set a Master Vault Key first, then run Manual / Instant Backup on demand or configure one Auto Backup schedule per site.

K

Master Vault Key (required for cloud)

On MigraSync → WP Backup, generate or paste your Master Vault Key and download the Recovery Sheet. Encrypted cloud backups cannot be restored without the same key. Store it in a password manager — MigraSync cannot recover a lost key.

M

Manual / Instant Backup

Open MigraSync → WP Backup, choose Manual / Instant Backup, select scope (database, media, plugins, themes), set an Auto purge policy for this backup, and click Start full backup. Progress appears in the wizard and under Recent Backup Jobs.

A

Auto Backup schedule

Choose Auto Backup to set frequency (daily, weekly, or monthly), trigger time in your site's local timezone, scope, and retention. Only one auto schedule is allowed per site — edit or terminate the existing schedule before creating a new one. Scheduled runs appear under Saved Schedule and Recent Backup Jobs.

R

Auto purge policy (retention)

Each backup includes an Auto purge policy — how long MigraSync keeps it in Managed Cloud (for example 1 Week through 1 Year, capped by your plan). Essential supports up to 30 days; Pro supports up to 365 days. Purge old jobs manually from Recent Backup Jobs to free storage quota. Auto purge runs while your subscription is active.

WP Backup and WP Restore require an Essential or Pro backup plan (or an active backup trial). See Pricing for current cloud storage limits. View pricing

5. WP Restore Wizard

WP Restore recovers your site from an encrypted MigraSync Managed Cloud backup. Use the guided wizard on MigraSync → WP Restore — same URL for disaster recovery, or another URL to clone to a new host or domain.

Restore procedure

  1. Open MigraSync → WP Restore (requires Essential or Pro backup plan and connected API key).
  2. Choose Restore to same URL or Restore to another URL (cross-site clone).
  3. Select a completed backup point from Available backups (click Refresh list if needed).
  4. Choose restore scope — Database is required; optionally include Media, Plugins, and Themes.
  5. Enter the Master Vault Key used when the backup was created.
  6. Confirm and start restore. Progress continues in the background — you may close the tab.
  7. When complete, reload the site and flush permalinks (Settings → Permalinks → Save).

EXPIRATION GRACE PERIOD POLICY

If your backup subscription expires, new backups are suspended immediately. However, your existing remote backups are preserved in MigraSync Managed Cloud during a grace period (7 days for trials, 30 days for paid plans). You can access and restore your site freely during this period.

6. WP-to-WP Migration & Server Cloning

Clone staging, move hosts, or change domains by backing up the source site to MigraSync Managed Cloud, then restoring on a fresh WordPress install with the same account API key. MigraSync automatically rewrites site URLs in the database for cross-URL restores.

1

Backup source site

On the live site, connect the plugin and run a Manual or Auto backup to MigraSync Managed Cloud. Wait until Recent Backup Jobs shows Completed.

2

Prepare destination

Install WordPress and the MigraSync Plugin on the new host or domain. Connect the same MigraSync account API key.

3

Cross-URL restore

On the destination, open WP Restore → Restore to another URL, pick the source backup, enter your vault key, and confirm. Update DNS when testing is complete.

7. SEO 301 Redirects (after Blogger migration)

Blogger URLs often differ from WordPress permalinks. During migration, MigraSync captures old-to-new URL pairs. After import, generate live 301 redirects so visitors and search engines reach the correct WordPress pages.

  1. Complete (or substantially finish) your Blogger migration.
  2. Open MigraSync → SEO 301 Redirects (SEO 301 Redirect Manager).
  3. Review captured vs live redirect counts and your package quota.
  4. Click Start SEO 301 Redirect and wait for the progress bar to finish.
  5. Test old Blogger URLs — they should redirect to the matching WordPress permalink.

Purging WordPress content for a fresh migration also clears stored SEO redirects. SEO redirects guide

More help