Run the scripts
Create a local export before the source disappears.
The current PluralBridge scripts are designed to export Simply Plural data into local files that remain under the user’s control.
Use the repository instructions as the command source
This page gives the public-facing shape of the workflow. The exact commands should be taken from the current PluralBridge repository documentation, because scripts may change as the export path improves.
Current workflow shape
- Download or update the PluralBridge repository from GitHub.
- Create a Simply Plural API token from inside the user’s Simply Plural account.
- Store the token locally as instructed by the repository documentation.
- Run the JSON export script.
- Confirm that JSON files were created in the local export folder.
- Run avatar and notes export steps where supported.
- Back up the exported files somewhere private and durable.
Expected local output
The current export path is intended to create local JSON files and related export folders. Depending on the user’s account data and the current script version, this may include members, groups, front history, custom fields, notes, avatars, timers, polls, friends, chat data, and manifest files.
Database migration
PluralBridge also includes SQL Server migration scripts that can turn exported JSON files into database tables, constraints, and readable views. That database path is mainly useful for developers, technically comfortable users, reporting, validation, and future viewer development.
Source and current documentation
Use the GitHub repository for the current scripts and exact run instructions: