I have a trusted technical helper
Ask them to sit with you, read the safety notes, install the requirements, and run the export scripts on a computer you trust.
Help me export
If you are not a software developer, you can still preserve your Simply Plural data.
The current PluralBridge tools may require help from someone comfortable with command-line work. This guide explains the choices, the safety rules, and what a successful export should leave on your machine.
The goal
The goal is to make a local copy of your Simply Plural data while the service and public API are still available. That local copy can later feed viewers, reports, databases, migration tools, and future preservation work.
Choose the path that fits you
I can follow careful steps
Start with the install page, then use the run page. Move slowly and keep your token and exported files private.
I need help before I run anything
That is a reasonable place to be. Read this page first so you know what to ask for and what information must stay private.
What your helper needs to know
- You create your own Simply Plural API token inside Simply Plural.
- The token should be treated like a password.
- The export should run on a computer you trust.
- The exported files may include member data, notes, avatars, front history, groups, custom fields, and other private System information.
- The exported files should stay out of public GitHub repositories, chat screenshots, paste sites, and public support threads.
What to protect
Protect the API token, the exported JSON files, notes, avatars, database files, screenshots of exported data, and backups. These files can contain private System information even when the filenames look harmless.
What gets created
The current export path creates local files on your computer. The main output is JSON data. Depending on what is available in your Simply Plural account, the export may also preserve notes and avatar images. Later PluralBridge tools may use the same preserved data for databases, reports, viewers, and migration work.
What success looks like
- You have exported files stored locally on a computer or drive you control.
- You have at least one backup copy somewhere safe.
- Your API token has not been posted or shared publicly.
- Your exported data has not been committed to GitHub or uploaded to a public site.
- You know where the exported files are and can find them again.
Where to go next
If you can follow careful steps, start with Install, then Run, then Safety. If you have a helper, ask them to read those same pages with you before touching the token or export files.
What is coming later
PluralBridge is moving toward clearer packages, launcher-style tooling, local viewers, and easier guides. The current priority remains preservation: get the data safely out while export access still exists.