Migrating settings

Who this guide is for

You are moving EdminBoost setup from one site to another, staging to production, or keeping a backup before big changes.

What gets migrated

Export/import moves EdminBoost configuration as one JSON file, including:

• Command Center (top bar, layout presets, role assignments, visibility, theme, Menu Studio, behavior)
• Productivity, Security, and Performance toggles
• White label settings

What does not move automatically

• Media files (admin favicon, background image, etc.) live in the Media Library. After import, re-attach images if attachment IDs on the new site do not match.
• Other plugins’ data (WooCommerce products, etc.)—only EdminBoost settings move.
• WordPress users and roles exist on the target site; role assignments import but the roles must already exist.

Before you migrate

1. On the source site: EdminBoost → Settings → Export settings.
2. Store the downloaded file safely (dated filename like export-2026-03-26.json).
3. Note WordPress and EdminBoost versions if source and target differ greatly.

Import on the new site

1. Install and activate EdminBoost on the target site.
2. Log in as an administrator.
3. EdminBoost → Settings.
4. Choose Import file (upload your JSON) or Paste JSON.
5. Click Import settings.
6. The page reloads when import succeeds.

Import replaces all current EdminBoost settings on that site. There is no undo—export first on the target if it already had config you care about.

After import — checklist

• Open Top Bar — confirm links still match plugins on the new site (some slugs differ).
• Open Menu Studio — custom links and order; re-save if you change anything.
• Open Layout Presets — role assignments and matrix; test each role.
• Theme — favicon/background if images are missing, pick media again on Appearance extras.
• Front-end / live bar — log in and click shortcuts and any drawer links.

Staging → production workflow

Common pattern:

1. Build and tune on staging; export JSON.
2. Deploy WordPress (database + files) as you normally would, or set up production fresh.
3. Import JSON on production if EdminBoost settings were not copied with the DB.
4. Re-test WooCommerce badges, custom menu links, and white label.

Deactivate vs delete (data on the old site)

• Deactivating EdminBoost leaves settings in the database.
• Deleting the plugin removes EdminBoost options. Export before delete if you need that layout later.

Tips

• One JSON file per site “profile” (client A, client B, agency default).
• After import, run through the client site setup or ecommerce guides once to validate role-specific views.
• EdminBoost does not send your JSON anywhere; export and import stay on your server unless you download or upload the file yourself.