How to Fix All-in-One WP Migration License or Pro Feature Confusion

If All-in-One WP Migration is showing fewer features than expected, the safest first move is to confirm which plugin and paid extensions are actually active before changing backups, licenses, or site files. Most confusion comes from mixing up the free plugin, the Pro extension, cloud storage extensions, role permissions, or an unsupported install location.

Quick checks before changing anything

Open Plugins > Installed Plugins and look for All-in-One WP Migration and Backup. The free plugin can export and import through its normal screens, but paid features depend on separate ServMask extensions being installed, activated, and licensed.

The official WordPress.org page for All-in-One WP Migration and Backup describes the base plugin as a migration and backup tool, while ServMask documents Pro features separately in its All-in-One WP Migration Pro Extension guide. That split matters: installing the free plugin does not automatically unlock Pro import behavior, cloud storage, or other extension-only options.

Check these in order:

1. Plugin status: the main All-in-One WP Migration plugin is active.
2. Extension status: the Pro, Unlimited, or cloud extension you paid for is also active.
3. License/account: the extension is connected using the license or account details from ServMask.
4. User role: you are logged in as an Administrator, not an Editor, Shop Manager, or custom role.
5. Menu visibility: the All-in-One WP Migration menu appears in wp-admin and includes the screen you need.

If the menu is missing or only some pages are visible, compare your case with ServMask’s access article for missing export, import, or backup pages. That points to permissions or capability handling rather than a broken backup file.

Match the symptom to the likely cause

Use this before reinstalling anything:

Symptom	Most likely cause	First fix
Pro, Unlimited, or cloud option is missing	Extension is not installed, inactive, or unlicensed	Check Plugins > Installed Plugins, then the extension settings
Import limit still appears	Pro/Unlimited extension is not active or not recognized	Reactivate the extension and confirm the license
Export to cloud storage is missing or fails	The specific cloud extension is missing, inactive, or disconnected	Reconnect that provider from the plugin’s settings
All-in-One WP Migration menu is missing	User role/capability issue or plugin conflict	Log in as Administrator, then test with other admin plugins disabled
JavaScript or JSON parse error appears during import/export	Browser-side script error, corrupted response, security plugin, cache layer, or server error interrupting the request	Check browser console and hosting error logs before retrying
Plugin works when installed normally but fails from mu-plugins	Unsupported manual placement or incorrect plugin URL/constants	Move it back to the normal plugins directory

Do not assume a license problem just because an import or export failed. A server timeout, blocked request, browser console error, or corrupted archive can look like a feature problem when the paid extension is working normally.

Confirm the installed plugin and extensions

Start in wp-admin:

1. Go to Plugins > Installed Plugins.
2. Search for All-in-One WP Migration.
3. Confirm the main plugin is active.
4. Look for the paid extension you expect to use, such as Pro, Unlimited, or a cloud storage extension.
5. If the extension is inactive, activate it.
6. If WordPress reports an activation error, stop there and save the error text before trying another fix.

WordPress loads normal plugins from the standard plugins directory, documented in the WordPress developer handbook’s plugins overview. Avoid moving All-in-One WP Migration into mu-plugins unless ServMask explicitly supports that setup for your version. Must-use plugins load differently in WordPress, and that can break assumptions a normal plugin makes about its URL or assets.

If the extension was downloaded from your ServMask account, use the current package from that account rather than an old ZIP stored locally. A stale extension can leave the free plugin active while paid screens stay unavailable.

Reconnect the license or cloud extension

If the paid extension is active but the feature is still missing, open the All-in-One WP Migration settings page for that extension and look for a license, account, or connection status.

For cloud storage features, reconnect the provider from the extension’s own settings instead of editing the WordPress database. If the authorization window fails, temporarily disable browser privacy extensions, allow pop-ups for the site, and retry from a fresh wp-admin session.

For license problems, check:

1. The license belongs to the correct ServMask product.
2. The license has not reached its activation limit.
3. The site URL in the account matches the current domain if the vendor ties activations to URLs.
4. The site can make outbound HTTPS requests from the hosting account.

If those checks are clean and the license still will not activate, contact ServMask with the product name, order email, license message, and current site URL. Do not send admin passwords in a support ticket.

Clear permission and admin conflicts

If the plugin is active but the menu is missing or only some pages appear, test from a full Administrator account first. Custom roles, membership plugins, admin menu editors, and security plugins can hide pages without changing the plugin files.

A safe test order:

1. Log in as the original site Administrator.
2. Temporarily disable admin menu customization plugins.
3. Temporarily disable role/capability plugins.
4. Reload wp-admin in a private browser window.
5. Check All-in-One WP Migration > Export, Import, and Backups again.

Change only one thing at a time. If the menu returns after disabling a role or admin menu plugin, the migration plugin is probably not the source of the problem.

Check failed imports and exports without guessing

When the visible feature is present but the task fails, separate license confusion from a runtime failure.

For export failures, try exporting to File before testing Google Drive, Dropbox, S3, or another remote destination. A successful file export means the base plugin can build an archive, and the problem is more likely the cloud extension, provider connection, or hosting outbound request.

For import failures, confirm the archive came from All-in-One WP Migration and was not renamed, partially uploaded, or truncated. If the browser shows a JSON parse error, open the browser developer console and check whether the failed request returned HTML, a login page, a firewall message, or a server error instead of JSON. That usually means something interrupted the request before the plugin could finish.

Also check the hosting panel’s PHP error log and web server error log around the exact time of the failure. A 403 points toward a firewall or security rule. A 500 points toward PHP/server failure. A timeout or memory error points toward hosting limits rather than licensing.

Optional SSH status check

If wp-admin is unavailable and you already have SSH with WP-CLI, you can check whether the main plugin is installed and active:

wp --skip-plugins --skip-themes plugin status all-in-one-wp-migration

Treat this as a narrow status check. It will not activate a paid license, reconnect a cloud account, or prove that import/export works. WP-CLI’s plugin command is documented in the official wp plugin reference.

Rollback and recovery

Before reinstalling extensions or changing plugin files, make sure you have a separate backup outside All-in-One WP Migration. Use your hosting backup system if available, or download a copy of wp-content and export the database from the hosting panel.

For a plugin-file rollback:

1. Download the current extension ZIP from your ServMask account.
2. Deactivate the affected extension in wp-admin.
3. Reinstall the extension from Plugins > Add New > Upload Plugin.
4. Reactivate it and reconnect the license if prompted.
5. Test the missing screen or feature before retrying a large migration.

If wp-admin breaks after activation, use SFTP or your host’s file manager to rename only the affected extension folder inside wp-content/plugins/. Leave the main All-in-One WP Migration plugin alone unless the main plugin is the one causing the fatal error.

How to confirm it worked

The fix is complete when the specific paid feature appears in wp-admin and a small, low-risk action succeeds.

For export confusion, create a small File export first. For cloud confusion, reconnect the provider and run a small backup to that destination. For import confusion, confirm the import screen recognizes the archive before attempting a large production restore.

Stop and contact ServMask or your host when:

1. The paid extension is active but still not recognized.
2. The license activation message says the license is invalid or over its limit.
3. The host logs show blocked requests, 403 errors, or server timeouts during import/export.
4. The plugin only fails when installed as a must-use plugin.
5. A backup archive appears corrupted or incomplete.

Send support the exact product name, plugin version, error message, destination type, and whether a local File export works. That gives them enough to separate account licensing, extension activation, and hosting limits without risking your site data.