Export & Import
Skelenote lets you export your data to standard formats and import from other tools.
Export Overview
Skelenote supports multiple export formats to suit different needs:
Markdown
.md
Obsidian, Notion, Bear, Git repos
HTML
.html
Sharing, printing, email
JSON
.json
Complete backups, data migration
Plain Text
.txt
Simple text extraction
.pdf
Formal documents, archiving
Export Formats
Markdown
The default export format. Produces standard Markdown files with YAML frontmatter that work with:
Obsidian
Notion (via import)
Bear
Any Markdown editor
Git repositories
Example output:
Options:
Include frontmatter - Adds YAML metadata at the top
Include title - Adds the title as an H1 heading
HTML
Creates a self-contained HTML file with embedded styling. Perfect for:
Sharing with non-technical users
Printing from a browser
Email attachments
Offline viewing
The HTML export includes:
Complete styling (no external CSS required)
Proper typography matching Skelenote's aesthetic
Responsive layout for different screen sizes
All images embedded as base64 data
JSON
Full backup format that preserves all metadata. Use this for:
Complete data backups
Migrating to another device
Data analysis
Programmatic access
JSON structure:
The JSON format includes:
All object properties exactly as stored
Rich text content in BlockNote JSON format
System metadata (created, updated, pinned, inboxed)
Version number for future compatibility
Plain Text
Extracts content without any formatting. Useful for:
Copying text to other applications
Text analysis tools
Accessibility needs
Maximum compatibility
Plain text export strips:
All formatting (bold, italic, etc.)
Images and embeds
Links (keeps link text only)
Frontmatter metadata
PDF
Creates a professionally styled PDF document. Ideal for:
Formal documentation
Long-term archiving
Printing
Sharing as read-only
PDF options:
Theme - Light or dark background
Include title - Show title at the top
Include metadata - Add type, dates, and properties
Page size - A4 or Letter
PDF exports use Skelenote's typography and maintain visual fidelity with the app.
Single Object Export
Export individual objects in any format.
How to Export
Open the object you want to export
Press
Cmd+Shift+Eor use the object menu (three dots)Select your preferred format
Configure format-specific options
Choose save location
File saves as
{title}.{ext}
Keyboard Shortcut
macOS
Cmd+Shift+E
Windows/Linux
Ctrl+Shift+E
Bulk Export
Export multiple objects at once to a ZIP archive.
How to Export
Open Settings (
Cmd+,)Go to Data section
Select export format:
Markdown ZIP - All objects as .md files
PDF ZIP - All objects as .pdf files
JSON Backup - Complete backup (single file)
Configure options:
Organize by type - Creates folders for each type
Include archived - Adds archived objects
Filter by type - Export only specific types
Click Export
Choose save location
Monitor progress indicator
ZIP Structure
With "Organize by type" enabled:
Without organization (flat structure):
Progress Tracking
For large exports (100+ objects), Skelenote shows real-time progress:
Progress Phases
Preparing
Counting objects, initializing export
Exporting
Converting each object to the target format
Compressing
Creating the ZIP archive
Complete
Export finished, file saved
Progress Indicator
The progress dialog shows:
Current object being processed
Progress bar (X of Y objects)
Current phase
Cancel button (stops export gracefully)
Tip: Large exports with many images take longer due to image processing. The "Exporting" phase shows which object is currently being converted.
Attachment Handling
Images and file attachments are handled differently depending on the export format.
Markdown Export
Single object:
Creates an
attachments/folder next to the .md fileCopies images to the attachments folder
Updates image links to relative paths:

Bulk export:
Single shared
attachments/folder in the ZIP rootDuplicate images are stored only once
All objects reference the shared folder
HTML Export
Images are embedded directly as base64 data URIs
No external files needed
Results in a fully self-contained HTML file
Larger file size but maximum portability
PDF Export
Images are embedded in the PDF
Supports PNG, JPEG, GIF, and WebP formats
Images are scaled to fit page width
Original aspect ratios are preserved
JSON Export
Image URLs are preserved as-is (not embedded)
Local file:// URLs point to original locations
Suitable for backup/restore on the same machine
For cross-machine backups, use Markdown ZIP
What Gets Exported
Text content
Yes
Yes
Yes
Yes
Yes
Formatting
Yes
Yes
Yes
Yes (raw)
No
Images
Copied
Embedded
Embedded
URLs
No
Links
Wiki-links
Clickable
Clickable
Raw
Text only
Properties
Frontmatter
Header
Optional
Full
No
Mentions
Wiki-links
Links
Text
Raw
Text
Backup Strategy
Recommended Approach
Weekly exports - Set a reminder to export weekly
Cloud storage - Save ZIPs to iCloud, Dropbox, or Google Drive
Version control - Optionally commit exports to a Git repo
Recovery Scenarios
Device lost/broken
Restore from backup + re-enter Skeleton Key
Accidental deletion
Use Time Machine (in-app) or restore from backup
Corrupted data
Export provides clean Markdown as fallback
Data Portability
Using with Obsidian
Exported files work directly in Obsidian:
Export from Skelenote
Extract ZIP to your Obsidian vault folder
Files appear with full formatting
Wiki-links ([[note-name]]) are compatible with Obsidian's linking.
Using with Git
For version-controlled notes:
Export to a Git repository folder
Commit changes
Push to GitHub/GitLab for cloud backup
Import Overview
Bring your notes, tasks, and projects from other tools into Skelenote.
Access: Settings (Cmd+,) → Data → Import
Supported Sources:
Notion
Databases and pages via API
Obsidian
Vault folder with wiki-links
Markdown
Individual .md files
All imported objects arrive in your Inbox for triage.
Import from Notion
Connect directly to your Notion workspace and import databases with intelligent type mapping.
Step 1: Create a Notion Integration
Click New integration
Name it (e.g., "Skelenote Import")
Select your workspace
Under Capabilities, enable:
Read content
Read user information (optional, for People properties)
Click Submit
Copy the Internal Integration Token
Step 2: Connect in Skelenote
Open Settings → Data → Import
Select Notion
Paste your integration token
Click Connect
Security note: Your token is never stored. It's only held in memory during the import session.
Step 3: Share Databases with Your Integration
In Notion, for each database you want to import:
Open the database page
Click ... (top right) → Connections
Select your integration
Only databases shared with your integration will appear in Skelenote.
Step 4: Select Databases
The import wizard shows all accessible databases with:
Page count - How many items will be imported
Auto-detected type - Skelenote's best guess (Task, Note, Project, etc.)
Confidence indicator - How sure we are about the type mapping
Check the databases you want to import.
Step 5: Review Type Mapping
For each selected database, confirm or change the Skelenote type:
Has Status, Due Date columns
Task
Has meeting attendees
Meeting
Named "Projects" or similar
Project
Has Areas/Categories
Area
Everything else
Note
Click on a database to expand property mapping options.
Step 6: Property Mapping
Skelenote auto-maps Notion properties to Skelenote properties:
Title
title/name
Object's main title
Rich Text
Text
Formatting preserved
Number
Number
Direct conversion
Select
Select
Options auto-created
Multi-select
Multi-select/Tags
Can map to tags
Date
Date
Converted to timestamp
Checkbox
Checkbox
Boolean values
Status
Select (status)
Task status mapping
URL, Email, Phone
Text
As plain text
Relation
@mention
Becomes mention in content
People
Skipped
Not currently mapped
Files & Media
Skipped
References only
Properties without a clear match are skipped by default. You can manually assign them or leave them skipped.
Step 7: Standalone Pages
Pages not in any database (workspace root pages) can be:
Imported as Notes - They'll appear in your Inbox
Skipped - Leave them in Notion
What Gets Imported
Content - Headings, paragraphs, lists, code blocks, quotes
Properties - Mapped according to your configuration
Nested content - Toggle blocks, callouts, columns (flattened)
Relations - Become @mentions linking to imported objects
Troubleshooting Notion Import
"Invalid token"
Regenerate token in Notion and reconnect
No databases shown
Share databases with your integration in Notion
Import stuck
Large workspaces take time; check progress indicator
Missing properties
Review property mapping; some types can't be mapped
Missing pages
Only pages in shared databases are accessible
Import from Obsidian
Import an entire Obsidian vault with wiki-links, hashtags, and frontmatter preserved.
How to Import
Open Settings → Data → Import
Select Obsidian
Choose your vault folder
Preview detected files
Adjust type mappings if needed
Click Import
What Gets Converted
Wiki-links → @mentions
Obsidian's [[note-name]] links become Skelenote @mentions. After import, clicking a mention navigates to the linked object.
Becomes a mention that links to the "Meeting Notes" object.
Hashtags → Tags
Obsidian #tags become Skelenote Tag objects:
#work→ Tag named "work"#project/alpha→ Tag named "project/alpha" (hierarchy preserved)
Tags are created automatically if they don't exist.
Frontmatter → Properties
YAML frontmatter is parsed into object properties:
Type Inference
Skelenote infers object types in this order:
Frontmatter
type:field - Explicit type winsFolder name - Files in
/tasks/become TasksContent patterns - Due dates suggest Task type
Default - Everything else becomes a Note
/tasks/ or /todo/
Task
/projects/
Project
/areas/
Area
/people/ or /contacts/
Person
/meetings/
Meeting
Troubleshooting Obsidian Import
Broken wiki-links
Links match by file name (case-insensitive)
Duplicate file names
First match used; check preview
Large vault slow
1000+ notes take a minute; progress shown
Special characters
File names are sanitized automatically
Missing tags
Check if hashtags use valid format: #tag-name
Import from Markdown
Import individual Markdown files with optional frontmatter.
How to Import
Open Settings → Data → Import
Select Markdown Files
Choose one or more
.mdfilesPreview parsed content
Adjust types if needed
Click Import
What Gets Parsed
YAML Frontmatter:
Title inference:
Uses frontmatter
title:if presentFalls back to first H1 heading
Otherwise uses filename
Type inference:
Uses frontmatter
type:if presentOtherwise defaults to Note
Import Tips
Best Practices
Start small - Import a test subset first to verify mappings
Review the preview - Check auto-detected types before importing
Clean up after - Review auto-created tags and merge duplicates
Process your inbox - Imported objects need triage like any other
After Importing
Check your Inbox for new objects
Review auto-created Tags (from hashtags or multi-select properties)
Verify @mention links resolved correctly
Archive or delete unwanted imports
Common Issues
Duplicate objects
Import creates new objects, not merge with existing
Missing wiki-links
Links need exact file name match to resolve
Slow import
Large datasets take time; progress indicator shows status
Property mismatch
Some Notion types can't map directly; adjust or skip
Too many tags
Multi-select fields can create many tags; clean up after
Frontmatter Reference
Exported YAML frontmatter includes:
id
Unique object ID
abc123-def456
type
Object type name
Task, Note, Project
created
Creation timestamp
2024-01-01T10:00:00Z
updated
Last modified
2024-01-10T15:30:00Z
archived
Archive status
true or omitted
pinned
Pin status
true or omitted
(properties)
Type-specific
status, due, priority, etc.
Property Types
Text
property: "value"
Number
property: 42
Date
property: 2024-01-15
Checkbox
property: true
Select
property: option-value
Relation
property: "[[Object Name]]"
Multi-relation
property: ["[[A]]", "[[B]]"]
Troubleshooting
Export is slow
Large vaults (1000+ objects) may take a minute. The progress bar shows status. PDF exports are slower than Markdown due to rendering overhead.
Images not appearing
For Markdown exports, check that the attachments/ folder was created alongside the .md file. For HTML and PDF exports, images should be embedded automatically.
File name conflicts
If multiple objects have the same title, files are numbered: note.md, note-1.md, etc.
Special characters in titles
Titles are sanitized for file systems. Characters like /, \, : become -.
Export format recommendations
Backup for restore
JSON
Moving to Obsidian
Markdown ZIP
Sharing with others
PDF or HTML
Archiving projects
Markdown ZIP
Printing
Data analysis
JSON
Last updated