Export & Import

Export & Import

SlideMind ships a single Export & Import page (accessible from the SlideMind menu and mirrored in Settings > Data tab) that handles every backup, migration, and cross-site transfer scenario. Both surfaces share the same layout.

Exporting

1. Check the sections you want to include: Courses, Modules, Slides, Custom templates, Learner memory, Memory definitions, Plugin settings.
2. To cherry-pick specific items within a section, click Choose specific items… and uncheck anything you want to leave out. For sections with more than 20 items, use the filter box to find items by title.
3. Click Download export file. The file is named slidemind-export-<host>-<YYYY-MM-DD>.json and uses the slidemind-export-v1 format.

Security note: API keys and license state are never included in any export file.

Importing

1. On the same page, drop a JSON file into the Import card or paste its contents into the textarea. Any SlideMind export format is accepted — the current slidemind-export-v1 as well as the two legacy formats (see Legacy format compatibility below).

2. Click Analyze file. SlideMind reads the file, lists each section’s contents, and marks any item whose title already exists on this site with an Exists badge.

3. For each flagged item, choose one of:

   • Skip — leave the existing item untouched and do not import this entry.
   • Duplicate — create a new copy alongside the existing item.
   • Overwrite — update the existing item’s fields while keeping its WordPress post ID, permalink slug, publication date, and any stored API key intact.

   Use the Default action for matches selector at the top of the preview to apply one choice to all flagged items at once.

4. Uncheck any item you do not want to import. Deselecting a parent (for example a course) automatically deselects its children.

5. If the file contains plugin settings and you want to apply them, tick Apply plugin settings from backup. Existing API keys and license activation stay untouched.

6. Click Import selected. A report summarizes how many items were created, overwritten, or skipped, and whether any holder parents were created automatically.

Orphan items and holder parents

When a file contains modules or slides whose parent course or module is not present in the file — and you have not deselected those items — SlideMind creates a holder course named Imported (orphan parents) — <date> and, if needed, a holder module named Imported slides. You can reorganize these items into the correct hierarchy after import.

Learner memory variables

Exports always include every row from the learner memory table, for backup and audit purposes. These rows are never re-imported, because they reference WordPress users and session IDs that do not exist on the target site. Re-importing them would silently attach data to the wrong learners or fail. Use exported files as a point-in-time archive of what each learner had stored. To restore learner memory on the same site, use a database-level backup instead.

Legacy format compatibility

The importer accepts files from any SlideMind version:

File signature	Origin
{"format": "slidemind-export-v1", ...}	Current format
{"slidemind_export_version": "2.0", "export_type": "bulk", ...}	v2.0 full backup
`{“slidemind_export_version”: “1.0”, “export_type”: “course	module

All three are converted transparently before the analyze/preview step. The export always produces slidemind-export-v1.

Per-listing scoped imports

Each list page (Courses, Modules, Slides) has an Import button that opens a scoped import modal. The modal uses the same analyze → preview → import flow, but restricts the import to that type and automatically attaches items to the parent you select (for example, attaching imported slides to a specific module). No holder parents are created for scoped imports.

---

API Key Per Course

Each course can have its own API key for cost tracking and isolation. The key cascades: Slide → Module → Course → Global settings. If a course has a dedicated key, all its modules and slides use it automatically unless overridden at a lower level.

This is useful for:

• Multi-client setups — track AI costs per client or project.
• Budget separation — different courses use different OpenRouter accounts.
• Agency plans — manage multiple sites with isolated billing.

Configure per-course keys in the course edit page under API Key.

---

Next steps

• Getting Started — Installation and first slide setup
• Core Features — Learner integration, Sandbox, Templates, Code Generator, Wizard
• Administration — Dashboard, analytics, settings, CORS
• FAQ — Common questions about SlideMind