OutlineWiki Notion Markdown & Attachment Bulk Import Runbook
Hostinger KVM NVMe
OutlineWiki 8GB pick (90,000 IOPS) — KVM 4 (4 vCPU / 16GB DDR5 / 200GB NVMe)
InterServer Price-Lock KVM & ZFS
Low-RTT node for outline Node.js + Hocu (19 ms CRDT sync)
UltaHost Dedicated EPYC VDS
Steady OutlineWiki secondary tier (25–100 collaborative editors)
Clean Notion exports before importing so UUID filenames do not break search.
Teams leaving Notion Plus ($10/seat/mo) or Business ($18/seat/mo) routinely export gigabytes of nested Markdown and PNG attachments.
On OutlineWiki, we advise normalizing Notion trailing 32-character hashes and pre-sizing your MinIO disk pool using s3_disk_gb = docs_media_gb * 1.25 before triggering bulk import jobs.
OutlineWiki Reference Configuration for Notion Markdown & Attachment Migration
# Strip Notion 32-char UUID suffix from exported markdown directories
find ./notion-export -depth -name "* *" | while IFS= read -r path; do
clean=$(printf "%s" "$path" | sed -E 's/ [0-9a-f]{32}(\.md)?$/\1/')
[ "$path" != "$clean" ] && mv -n "$path" "$clean"
doneOutlineWiki Implementation Checklist: Notion Markdown & Attachment Migration
Phase 1: Notion Markdown & Attachment Migration
Export Notion workspace as Markdown & CSV with subpages included, excluding empty trash archives.
Phase 2: Notion Markdown & Attachment Migration
Measure raw attachment folder size in GB and multiply by 1.25 to verify MinIO NVMe or InterServer Storage headroom.
Phase 3: Notion Markdown & Attachment Migration
Run the OutlineWiki UUID normalization pass so internal cross-page links resolve cleanly after import.
Phase 4: Notion Markdown & Attachment Migration
Import top-level Collections sequentially in 500 MB batches so BullMQ worker queues stay under 1,200 MB RAM.
OutlineWiki Infrastructure Recommendation for Notion Markdown & Attachment Migration
Audit 10 random imported pages for broken image URLs before canceling Notion seats.
In our audit on OutlineWiki, teams with over 65 GB of Notion diagrams save the most by pairing a Hostinger KVM 2 compute host ($11.99/mo) with an InterServer 1 TB Storage VPS ($6.00/mo Price-Lock) as the MinIO S3 target.
OutlineWiki Hardware Ledger: NVMe Throughput vs Base Price
Packet-to-Disk Path for outline Node.js + Hocuspocus Yjs CRDT + OIDC on OutlineWiki
[+] Key Infrastructure Pros
- Keeps outline.env buffers stable at 100 collaborative editors via 8GB compute.
- Protects 19 ms CRDT sync objectives under heavy Postgres tsvector document graph + MinIO assets writes (90,000 IOPS).
- Trims OutlineWiki 3-year infrastructure bills 70%–85% versus metered SaaS seats.
[-] Operational Constraints
- Unlocking $10.49/mo on Hostinger KVM NVMe depends on annual commitment rather than 1m billing.
- Base OS templates need outline.env tuning (WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150) before peak load.
Deploy This OutlineWiki Stack If
- DevOps squads standardizing outline Node.js + Hocuspocus Yjs CRDT + OIDC (100 collaborative editors) on KVM nodes.
- Builders needing root access to set WEB_CONCURRENCY=4 & COLLABORATION_MAX_CLIENTS=150 in outline.env.
When To Choose Alternatives
- Two-day load tests where InterServer Price-Lock KVM & ZFS pay-per-hour beats annual commitments.
- Mandates requiring vendor-staffed 24/7 NOC contracts with zero SSH access.
$10.49/mo