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), optional chat/ledger/MCP cache | Default no physical data; optional Include physical data files. No user_knowledge, global config |
| 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; each workspace optional physical data | Still Rebind/unpack folders, re-enter passwords |
Product promise: Projects carry analysis artifacts; Workspaces carry working environment (handoff, new machine; physical data off by default, optional pack); Application carries who you are; none include license or live DB passwords—Rebind/unpack and reconnect on 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 — optional ledger, chat sessions, MCP cache, Include physical data files (Referenced in SQL tabs / All registered)
- Application profile — User Memory merge/replace
- Full backup — multiple workspaces + Application; per-workspace physical data same as Workspace
Details: USER_GUIDE §11.1.0–11.1.3.
Workspace import: 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" | Default no; optional physical data on export for machine moves |
| "Share analysis = Workspace" | Cross-role Plan/Report review usually Project; Workspace is full environment |
One thing to do now
Drill Export Workspace → Import as new workspace → Rebind same folder; optionally small bundle with Include physical data files.