Notebook Export & Import
Export and import your notebooks for backup, migration, and data portability.
Overview
Export: Download your notebooks in a standardized JSON format Import: Upload and restore notebooks from exported files Use Cases: Data backup, environment migration, no vendor lock-in, developer workflows
Export Features
Accessing Export
- Open your user profile
- Navigate to the Settings tab
- Find the AI Features section
- Click Export Notebooks
Export Options
Content Selection
- Knowledge Files: Include attached documents and files
- Artifacts: Include generated code, documents, and other artifacts
- Tools: Include custom tools and configurations
- Agents: Include AI agents and their settings
- Images: Include embedded images (as base64)
Privacy & Metadata
- Include Usage Metadata: Export token usage, costs, model information
- Anonymize Export: Remove user-identifying information
- Maximum File Size: Set limit for embedded files (larger files referenced by URL)
Filtering Options
- Date Range: Export only notebooks from specific time periods
- Specific Notebooks: Choose individual notebooks to export (coming soon)
Export Process
- Configure your export options
- Click Export Notebooks
- System processes all selected notebooks and attachments
- Download link provided when complete
- File downloaded as
notebooks-[user]-[date].json
Export Format
The export creates a JSON file with this structure:
{
"exportVersion": "1.0.0",
"exportedAt": "2024-01-15T10:30:00Z",
"platform": "lumina5",
"notebooks": [
{
"id": "notebook-123",
"name": "My Notebook",
"chatHistory": [...],
"knowledge": [...],
"artifacts": [...],
"tools": [...],
"agents": [...]
}
]
}
Import Features
Accessing Import
- Open your user profile
- Navigate to the Settings tab
- Find the AI Features section
- Click Import Notebooks
Import Methods
File Upload
- Drag and drop exported JSON files
- Click to browse and select files
- Supports files up to 50MB
JSON Data
- Paste exported JSON data directly
- Useful for copying between browsers/sessions
- Validates JSON format before import
Import Options
Conflict Resolution
- Skip: Ignore notebooks with existing names
- Rename: Add suffix to duplicate names (e.g., "Notebook (2)")
- Overwrite: Replace existing notebooks completely
- Merge: Append chat history to existing notebooks
Content Selection
- Knowledge Files: Import attached documents
- Artifacts: Import generated content
- Tools: Import custom tools
- Agents: Import AI agents
Advanced Options
- Preserve Original IDs: Keep source IDs (useful for developers)
- Name Prefix: Add prefix to all imported notebooks
- Target User: Import to different user (admin only)
Import Process
- Select import method (file or JSON)
- Configure import options
- Upload file or paste JSON data
- Click Import Notebooks
- System processes and validates data
- Notebooks added to your account
- Summary report shows results
Developer Use Cases
Environment Migration
# Export from staging
curl -X POST /api/notebooks/export \
-H "Authorization: Bearer $STAGING_TOKEN" \
-d '{"includeKnowledge": true}' \
> staging-notebooks.json
# Import to production
curl -X POST /api/notebooks/import \
-H "Authorization: Bearer $PROD_TOKEN" \
-F "file=@staging-notebooks.json" \
-F "conflictResolution=rename"
Cross-Account Testing
- Export notebooks from production account
- Import to test account with
preserveIds: false - Test features without affecting production data
- Clean separation of environments
Backup & Restore
- Schedule regular exports for backup
- Store export files in version control or cloud storage
- Quick restore capability for disaster recovery
- Maintain data history and versioning
Data Handling
Security
- Exports include full chat history and attachments
- Sensitive data (API keys, tokens) should be reviewed before sharing
- Anonymization option removes user-identifying information
- Files encrypted in transit and at rest
Performance
- Large notebooks may take time to export/import
- Progress indicators show processing status
- Bulk operations optimized for efficiency
- Asynchronous processing prevents timeouts
Compatibility
- Format Version: Current version 1.0.0
- Backward Compatibility: Newer versions support older formats
- Cross-Platform: Works between different platform instances
- Future-Proof: Extensible format for new features
Limitations
Current Restrictions
- Export file size limited by browser memory
- Very large attachments may be referenced rather than embedded
- Some system-generated content may not be portable
- Real-time collaboration data not included
Known Issues
- Image exports may be large due to base64 encoding
- Tool configurations may need adjustment in target environment
- Agent settings might reference unavailable resources
- Date/time zones preserved as UTC