# How To Export, Import and Migrate BetterShield Settings?

Export settings as JSON, preview an import, apply selected changes, or bring over recognized settings from another plugin.

In **[BetterShield](/)**, use **BetterShield › Settings › General › Plugin data & tools › Move settings between sites**.

## What it does

**Export settings** downloads `bettershield-settings.json`. **Import a settings file…** reads a JSON file and shows what will change. The final button says **Make this change** or **Make these N changes**. Nothing changes during preview.

The file can carry hardening, password, sign-in, two-factor, passkey, security contact, alert, agent, password-confirmation, and deletion choices. It does not carry enrollments, sessions, list authorship, the recovery link, alert recipients, or what each address chose. The file can reveal block lists and the sign-in address, so keep it private.

Recognized settings left by another security plugin can also appear with **Preview import**. BetterShield reads that plugin's settings but does not change or deactivate it.

<span id="set-it-up" aria-hidden="true"></span>

## Step 1: Export, Import and Migrate BetterShield Settings

Export on the source site. On the destination, choose the file, read every plan row and any item not carried, then apply the shown changes.

<figure class="doc-shot">
  <img src="/docs/screenshots/move-settings-between-sites.png" alt="Move settings between sites row with Export settings and Import a settings file controls." width="1960" height="264" loading="lazy" decoding="async">
  <figcaption>An import is planned and shown before any setting changes.</figcaption>
</figure>

## Import supported settings from another plugin

Quick Setup and **Settings › General** can preview supported settings from Wordfence, Kadence Security, All-In-One Security, Really Simple Security, Limit Login Attempts Reloaded, Loginizer, Security Optimizer and Login Lockdown. The preview lists each change and what stays behind. Review it before applying.

A settings file does not carry two-factor enrollments. Moving a supported authenticator app when its original plugin is deactivated is a separate process: see [Move existing two-factor accounts](/docs/migrate-two-factor/).

## Recommended settings

Import into staging first. Keep the export in private storage and compare the destination's recovery and recipient settings separately.

## What it can break and how to undo

An import can weaken or conflict with the destination's current configuration. Each changed setting receives its own history entry. Reverse supported items one at a time. There is no single whole-import rollback.

<span id="check-it-is-working" aria-hidden="true"></span>

## Final Outcome

The receipt should count applied, undone, changed, failed, and skipped items. Review the destination screens afterward.

<figure class="doc-shot">
  <img src="/docs/screenshots/move-settings-between-sites.png" alt="Move settings between sites row with Export settings and Import a settings file controls." width="1960" height="264" loading="lazy" decoding="async">
  <figcaption>Example Move settings between sites view. Check the saved values and status on your own site.</figcaption>
</figure>

## Related

- [Put a settings change back](/docs/restore-settings-change/)
- [General settings](/docs/general-settings/)
- [Set up recovery](/docs/set-up-recovery/)

This is how you can export, import and migrate BetterShield settings.

Getting Stuck? Feel free to contact our [Dedicated Support Team](/support/).