Export or Import Fediverse Configuration
Use configuration export and import when you want to repeat a working Fediverse setup across sites or preserve reusable settings before major changes. This saves time and reduces mistakes compared with rebuilding the configuration by hand.
Before you begin
- You need a
Prolicense. The transfer toolbar actions are not available in lower tiers. - You need Joomla Administrator access to the Fediverse component.
- Import replaces the current portable Fediverse configuration on the target site.
- Export and import do not move runtime federation history or cryptographic identity material.
What the package includes
- Fediverse component options except local license data
- Fediverse scheduler task settings
- per-user federation settings
- per-content federation settings
- domain policies
- OAuth clients
What the package does not include
- the current site’s license key
- the current site’s LemonSqueezy activation binding
- local actors
- signing keys
- followers
- inbox, outbox, and delivery history
- other runtime federation records
Export a package
- Open
Components -> Fediverse -> Dashboard. - In the toolbar, select
Export Configuration. - Save the downloaded JSON file in a secure location.
Import a package
- Open
Components -> Fediverse -> Dashboardon the target site. - In the toolbar, select
Import Configuration. - In the import dialog, choose the exported JSON file.
- Select the confirmation checkbox.
- Select
Import Configuration. - Wait for Joomla to reload the dashboard and show the success message.
Check your result
- Open the Fediverse settings or the relevant admin views that the package should affect.
- Confirm the expected scheduler settings, domain policies, user settings, content settings, or OAuth clients are present.
- Open
Users -> User Actions Log. - Set
ExtensiontoFediverse Integration. - Confirm Joomla recorded an import or export action.
Troubleshooting
- If the transfer buttons are not available, confirm the site has an
active
Prolicense. - If Joomla reports that the package is invalid, export a fresh package from a working Fediverse site and retry the import.
- If the import button does nothing, confirm you selected a file and enabled the confirmation checkbox.
- If expected runtime data is missing after import, review the package scope. Runtime queues, actors, followers, and keys are intentionally excluded.