evernote-migration-deep-dive
Deep dive into Evernote data migration strategies. Use when migrating to/from Evernote, bulk data transfers, or complex migration scenarios. Trigger with phrases like "migrate to evernote", "migrate from evernote", "evernote data transfer", "bulk evernote migration".
What this skill does
# Evernote Migration Deep Dive
## Current State
!`npm list 2>/dev/null | head -5`
## Overview
Comprehensive guide for migrating data to and from Evernote, including ENEX export/import, bulk API operations, format conversions (ENML to Markdown, HTML to ENML), and data integrity verification.
## Prerequisites
- Understanding of Evernote data model (Notes, Notebooks, Tags, Resources)
- Source/target system access credentials
- Sufficient API quota for migration volume
- Backup strategy in place before starting
## Instructions
### Step 1: Migration Planning
Assess the migration scope: count notes, notebooks, tags, and total resource size. Estimate API call count and quota consumption. Plan for rate limits (add delays between operations).
```javascript
async function assessMigration(noteStore) {
const notebooks = await noteStore.listNotebooks();
const tags = await noteStore.listTags();
let totalNotes = 0;
for (const nb of notebooks) {
const filter = new Evernote.NoteStore.NoteFilter({ notebookGuid: nb.guid });
const spec = new Evernote.NoteStore.NotesMetadataResultSpec({});
const result = await noteStore.findNotesMetadata(filter, 0, 1, spec);
totalNotes += result.totalNotes;
}
return {
notebooks: notebooks.length,
tags: tags.length,
totalNotes,
estimatedApiCalls: totalNotes * 2 + notebooks.length + tags.length,
estimatedTimeMinutes: Math.ceil((totalNotes * 2 * 200) / 60000) // 200ms per call
};
}
```
### Step 2: Export from Evernote
Export notes in three formats: ENEX (Evernote's XML format, preserves everything including resources), JSON (structured data for programmatic use), or Markdown (human-readable, loses some formatting).
```javascript
async function exportToMarkdown(noteStore, noteGuid) {
const note = await noteStore.getNote(noteGuid, true, true, false, false);
const text = enmlToMarkdown(note.content);
return {
title: note.title,
content: text,
tags: note.tagNames || [],
created: new Date(note.created).toISOString(),
resources: (note.resources || []).map(r => ({
filename: r.attributes.fileName,
mime: r.mime,
size: r.data.size
}))
};
}
```
### Step 3: Import to Evernote
Convert source data to ENML format, create notebooks to match source structure, and bulk-create notes with rate limit handling. Verify each import by comparing note counts and content hashes.
### Step 4: Migration Runner
Build a migration runner with progress tracking, checkpointing (resume from failure), and verification. Log every operation for audit trail.
For the full migration planner, ENEX parser, format converters, migration runner, and verification tools, see [Implementation Guide](references/implementation-guide.md).
## Output
- Migration assessment tool (note count, estimated time, quota needs)
- ENEX, JSON, and Markdown exporters
- ENML importer with format conversion
- Migration runner with progress tracking and checkpoint/resume
- Post-migration verification (count comparison, content hash check)
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `QUOTA_REACHED` | Upload quota exceeded during import | Wait for quota reset or upgrade account tier |
| `RATE_LIMIT_REACHED` | Too many API calls during bulk migration | Increase delay between operations, use checkpointing |
| `BAD_DATA_FORMAT` | Source content not valid ENML | Validate and sanitize content before import |
| Lost resources | Attachments not migrated | Verify resource hashes match after migration |
## Resources
- Evernote Export Format (ENEX)
- [ENML Reference](https://dev.evernote.com/doc/articles/enml.php)
- [API Reference](https://dev.evernote.com/doc/reference/)
- [Synchronization](https://dev.evernote.com/doc/articles/synchronization.php)
## Examples
**Export all notes to Markdown**: Iterate through all notebooks, export each note as a Markdown file with frontmatter (title, tags, date), save resources to `assets/` directory, preserving notebook-as-folder structure.
**Import from Notion**: Parse Notion export (Markdown + CSV), convert to ENML, create matching notebooks, and bulk-import with checkpoint/resume for large exports (10,000+ pages).
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.