Back to Community

Troubleshooting Common 'json value isn't an array VALUE: NULL' Errors in Duplicator

38 threads Sep 11, 2025 PluginDuplicator

Content

Understanding the 'json value isn't an array VALUE: NULL' Error

If you're using the Duplicator plugin for WordPress migrations, you might encounter a confusing error message: json value isn't an array VALUE: NULL. This error typically appears during the deployment phase (Step 1 of 2) of the migration process, often when moving a site to a new hosting provider.

Why Does This Error Occur?

Based on community reports and troubleshooting threads, this error is not caused by a single issue but rather can be triggered by several underlying problems:

  • Database Engine Mismatch: The most common cause appears to be a mismatch between database engines, particularly when migrating from MySQL to MariaDB or between significantly different versions of these systems.
  • Corrupted Package Files: The installer might be attempting to read package data that has become corrupted or incomplete.
  • Insufficient Server Resources: Although less common, inadequate disk space or memory on the destination server can sometimes manifest as this error.
  • Plugin Conflicts: In some cases, other plugins might interfere with the serialization process that Duplicator uses.

How to Resolve the 'json value isn't an array' Error

Solution 1: Address Database Compatibility Issues

If you're migrating between different database systems (e.g., MySQL to MariaDB) or significantly different versions:

  1. Check the database version on both your source and destination servers during the validation process.
  2. If possible, try to match the database engines between source and destination. Some users have reported success by changing the destination server's database engine to match the source.
  3. If matching isn't possible, ensure both systems are running updated, stable versions.

Solution 2: Verify Package Integrity

Since this error often occurs when the installer cannot properly read the package data:

  1. Recreate the package on the source site. Sometimes a fresh build resolves serialization issues.
  2. Ensure the entire package (both archive and installer files) is downloaded completely and uploaded intact to the destination server.
  3. Verify file permissions on the destination server allow proper reading of all package files.

Solution 3: Check Server Resources

Although you might have already addressed disk space issues, consider:

  1. Verifying that both temporary directory and final destination have adequate space
  2. Checking PHP memory limits on both source and destination servers
  3. Ensuring maximum execution time values are sufficient for the migration process

Solution 4: Temporary Plugin Deactivation

Some users have resolved various Duplicator issues by:

  1. Using the installer's Safe Mode (Basic) option which temporarily deactivates plugins
  2. Manually deactivating potentially conflicting plugins before package creation
  3. Specifically examining any plugins that handle serialized data (like ACF) for issues

When to Seek Additional Help

If these solutions don't resolve your issue, the problem might be more specific to your server configuration. In such cases, checking the installer-log.txt file can provide more detailed error information that might point to the root cause. The Duplicator team maintains detailed documentation that covers many specific error scenarios and their resolutions.

Remember that migration issues can be complex and often depend on specific server configurations. The solutions outlined here address the most common scenarios reported by users experiencing this particular JSON error.

Related Support Threads Support