Readable bundles and context handoff
Unencrypted Workspace exports use .lantide.zip, readable by standard ZIP tools. Encrypted Workspace exports keep .lantide; old bundles remain importable. A generated root README indexes artifacts, data entry points, actual contents, and available analysis history. Read it independently or use the latest Lantide client for full editing; external sources may still be needed to rerun work. Editing and re-zipping a bundle does not guarantee it can be imported.
Available analysis-context snapshots and stable source IDs travel with the Workspace bundle; imports rebuild context indexes. Native tracking tokens, machine-local recovery paths, and transaction journals do not travel; rebind on another computer. Direct Workspace physical-data export blocks missing or out-of-scope files by default. Explicitly allowing an incomplete bundle retains warnings and is not a complete backup.
For a new import with physical data, choose a dedicated container: initial data restores into main/ and Additional folders into additional//. Neither directory may already be occupied. Choose a custom folder can override the Additional base. Re-enter database passwords and reconnect sources after import.
Read time: ~8 minutes · Series: Platform Admin practice · Previous: Workspace and data folder · Next: MCP Sources basics
Four bundle types (remember this table)
| Bundle | Answers | Includes | Excludes |
|---|---|---|---|
| Project | Share this analysis context and results? | Plan, Report, Reference, project knowledge, annotation/HTML/viz sidecars | Workspace SQL tabs, connections, physical data files |
| Workspace | Continue same environment or new machine? | Settings, projects, connection/MCP config (no passwords), ledger, MCP cache, and by default all local files in the initial data folder and Additional folders; chat optional | No user_knowledge, global config, Cloud Folder, or remote database contents |
| Application profile | Cross-workspace Agent memory? | User Memory, knowledge/memory settings, optional AI prefs | License, data files, workspace bodies |
| Full backup | Move everything at once? | Multiple nested Workspaces + Application; physical data and MCP cache are opt-in per workspace | Still Rebind/unpack folders, re-enter passwords |
Product promise: Projects carry analysis artifacts; Workspaces carry working environment (handoff, new machine; complete local working files are included by default); Application carries who you are; none include license or live DB passwords—reconnect external sources on the new machine.
Full selector: USER_GUIDE §11.1.0.
Project or Workspace?
| Scenario | Recommendation |
|---|---|
| PM / business review Plan, accept Report (annotate) | Project |
| External meeting numbers only, no Lantide install | Report HTML (Business: HTML Report) |
| Analyst A → B handoff (SQL tabs, connections) | Workspace (optional chat sessions) |
| New computer | Workspace or Full backup |
| Move Plan/Report only; recipient connects DB | Project |
Export/import entry points
Title bar UsersRound → Export… / Import…:
- Project — also project right-click Export project…
- Workspace — ledger and MCP cache included by default; chat optional; Include files from local data folders defaults to All files in data and Additional folders with Balanced compression, and can be turned off or narrowed to Referenced / All registered data. Deduplicated physical bytes strictly over 200 MiB require confirmation
- Application profile — User Memory merge/replace
- Full backup — multiple workspaces + Application; per-workspace physical data and MCP cache are opt-in
Details: USER_GUIDE §11.1.0–11.1.3.
Workspace import: update, copy, or Rebind
After you choose a bundle, Lantide compares its workspace identity and version history with local workspaces:
- Same workspace history: choose Update existing workspace or Import as separate copy. An update preserves local folder locations, compatible credentials, and governance settings, and keeps the previous version for Restore Previous Version.
- No matching workspace: use the new-workspace Rebind wizard below.
- Local changes, an older bundle, or divergent history are shown as explicit warnings. Lantide does not attempt a silent file-by-file merge, and an interrupted update is recovered from its journal on the next launch.
New-workspace Rebind wizard (5 or 6 steps)
Without physical data (5 steps):
- Choose
.lantide, preview - New workspace name (no collision)
- Pick local folder matching original load dir (matched / missing files shown)
- Confirm connection and MCP lists (all disconnected)
- Import → Reconnect databases, Reconfigure MCP, Run Source Run, Refresh schema if needed
With physical data (6 steps): after step 3 add Review files to extract—unpack dir, resolve conflicts (Replace / Rename imported / Keep existing), then connections and import.
Passwords never in bundle—re-enter in Connections after import. Encrypt bundle needs passphrase custody (backup & security).
Common misconceptions
| Myth | Reality |
|---|---|
| "Import then query immediately" | Without physical data: Rebind + reconnect DB + often Source Run; with physical data still reconnect external DB |
| "Copy workspaces folder manually" | Path binding breaks; use official .lantide |
| "Project export includes data" | No CSV bodies; recipient needs data or connections |
| "Workspace never includes CSV" | Workspace currently includes complete local folder files by default; turn this off or narrow the scope when they should not be shared |
| "Share analysis = Workspace" | Cross-role Plan/Report review usually Project; Workspace is full environment |
| "Importing the same Workspace always creates another one" | Related history can update the existing workspace or be imported explicitly as a separate copy |
One thing to do now
Practice Export Workspace → Update existing workspace → Restore Previous Version, then try Import as separate copy and any required Rebind. Optionally repeat with a small bundle that includes physical data.