Private-beta migration pilot
Move from Archivist AI without rebuilding your campaign.
Archivist lets campaign owners export their data as an Obsidian Vault, Markdown files, or HTML. Everlore is preparing an import workflow that preserves the useful structure while giving you a chance to review what becomes Everlore canon.
Status: the automated importer is planned, not yet generally available. Early migrations will be handled through the private-beta pilot.
Export your campaign
Choose a campaign-wide Obsidian Vault export with all desired content groups and preserved wiki links.
Preview the import
Everlore detects sessions, entities, quests, journals, relationships, assets, and anything that needs a decision.
Approve the result
Review ambiguous identities and content boundaries before the imported campaign becomes your Everlore wiki.
Recommended Archivist export
Use an Obsidian Vault ZIP with wiki links preserved.
- 1Open the campaign in Archivist and go to Campaign Settings.
- 2Select Export Campaign Data.
- 3Choose Campaign-wide scope and Obsidian Vault format.
- 4Select the content groups you want and preserve
[[wiki links]]. - 5Download the ZIP and keep an untouched backup.
These steps reflect Archivist's official export documentation checked July 15, 2026. Export options may change.
Expected mapping
What Everlore can carry forward
API-assisted migration can fill export gaps.
Archivist's official API exposes campaigns, sessions, Markdown transcripts, hierarchical beats, moments, Compendium entities, quests, links, journals, and folders. An optional one-time API import could preserve more exact identifiers and provenance than a file export alone.
API access requires a paid Archivist subscription, and its keys are broadly capable. Everlore will not ask users to send a key by email or paste one into support chat. Any future connection must be server-side, read-only in behavior, short-lived, redacted from logs, and deleted after import.
Migration integrity
Imported summaries are not the same as primary evidence.
A transcript records what was said. A summary, timeline beat, or entity description is an interpretation that may already contain AI output or human corrections. Everlore's migration design keeps those categories distinct: transcripts become source material, user-authored journals remain authored material, and generated descriptions retain their imported provenance.
- Original external IDs retained for traceability.
- No invisible rewriting during import.
- Duplicate and identity preview before apply.
- Atomic import with a rollback path.
- Private material remains clearly separated.
- An import report explains skipped content.
Official references
Review Archivist's current campaign export documentation, developer guide, and API reference before exporting. Everlore is not affiliated with Archivist AI.
Bring the history with you
Help shape the Archivist migration pilot.
Join the waitlist and mention Archivist in the campaign or notes field. Never submit an Archivist API key.
Join the waitlist