[{"data":1,"prerenderedAt":262},["ShallowReactive",2],{"seo-verification":3,"blog-migrate-from-papermerge-to-paperless-ngx-en":6},{"google":4,"bing":5},"EycwPY2XMyTkVzas3n1ygeNJFGAH513qrMjfDljzsMQ","",{"key":7,"data":8},"blog-migrate-from-papermerge-to-paperless-ngx-en",{"id":9,"slug":10,"slugs":11,"title":15,"excerpt":16,"readTime":17,"views":18,"isPinned":19,"publishedAt":20,"updatedAt":21,"category":22,"categories":28,"featuredImage":30,"bgImage":31,"posterImage":32,"relatedSolution":33,"intro":36,"sections":37,"ctaTitle":185,"ctaBody":186,"ctaButton":187,"ctaUrl":188,"relatedPosts":189},377,"migrate-from-papermerge-to-paperless-ngx",{"fr":12,"en":10,"ar":13,"es":14},"papermerge-vers-paperless-ngx-migration","الهجرة-من-papermerge-إلى-paperless-ngx","migrar-de-papermerge-a-paperless-ngx","Migrate from Papermerge to Paperless-ngx","Papermerge is going SaaS: maintainer seeks a successor before Oct. 5, 2026. Migrate to Paperless-ngx, an actively maintained GPL-3.0 community fork.",10,0,false,"2026-09-25T00:00:00+00:00","2026-09-25T23:43:02+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},7,"Self-hosting","self-hosting","bg-indigo-500\u002F10 text-indigo-400","cloud",[29],{"id":23,"name":24,"slug":25,"color":26,"icon":27},null,"\u002Fblog\u002Fcovers\u002Fbg.svg","\u002Fblog\u002Fcovers\u002Fpapermerge-vers-paperless-ngx-migration-poster.svg",{"categorySlug":34,"appSlug":35},"collaboration-productivity","paperless-ngx","On September 5, 2026, Eugen Ciur — the sole maintainer of papermerge-core — opened issue #1318 to announce a full pivot to Papermerge Cloud, a paid SaaS product. Without a community maintainer by October 5, 2026, the repository will be archived and will receive no further security updates. If your team archives documents on a self-hosted Papermerge instance, this thirty-day window is the signal to migrate. Paperless-ngx — a GPL-3.0 community fork with ~23,000 GitHub stars and an official Docker Compose file — is the natural successor: it covers all of Papermerge's features and adds multi-language OCR, tags, correspondents, and S3-compatible storage.",[38,41,44,46,55,57,59,67,69,109,111,113,121,123,150,152,154,160,163,165,167,173,175,181,183],{"type":39,"body":40},"h2","The warning signal: papermerge-core issue #1318",{"type":42,"body":43},"p","On September 5, 2026, Eugen Ciur published issue #1318 on the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fciur\u002Fpapermerge-core\">papermerge\u002Fpapermerge-core\u003C\u002Fa> repository with an unambiguous title: \"Looking for a maintainer\". The announcement is direct: Papermerge will become a commercial SaaS product under the name Papermerge Cloud. The open source project is looking for a community maintainer within a thirty-day window. Without an identified maintainer, the repository will be archived around **October 5, 2026** — tickets will remain visible but no further commits will be accepted.\n\nThis scenario is structurally different from a simply inactive project. An archived repository receives no security patches. Papermerge v3.x relies on FastAPI, React, and a REST API — a modern architecture, but one whose dependencies (Python, FastAPI, OCR libraries) regularly publish critical updates. Continuing to run an unmaintained instance means silently accumulating a security debt.",{"type":39,"body":45},"What you lose by staying on a frozen Papermerge",{"type":47,"items":48},"ul",[49,50,51,52,53,54],"**No more security patches**: any vulnerability discovered after archiving will remain open — FastAPI and its dependencies publish several advisories per month","**Python compatibility declining**: new Python versions drop deprecated APIs; an OS update is enough to break the environment","**Orphaned plugins and integrations**: third-party connectors (scanners, mail clients, webhooks) will no longer be updated to follow Papermerge's REST API evolution","**No official schema migrations**: if a database bug is discovered, no fix will come from the archived repository","**No contractual support coverage possible**: no vendor will cover an installation on an archived project","**Ecosystem closing in**: official Docker images stop being published, and unofficial images introduce a supply chain risk",{"type":39,"body":56},"Why Paperless-ngx is the natural successor",{"type":42,"body":58},"**Paperless-ngx** is a community fork of paperless-ng, itself derived from Daniel Quinn's original Paperless project. It is published under the **GPL-3.0** license, counts ~23,000 stars on GitHub as of September 25, 2026, and receives regular updates from a distributed team of about ten active contributors — no single maintainer.\n\nThe architecture is more mature than Papermerge v3.x for SME use: Django as the backend, Celery for asynchronous tasks, PostgreSQL or SQLite as the database, and an integrated Angular frontend. The official Docker Compose file — maintained in the repository — deploys everything with a single command. Volumes persist documents, the database, and index data.",{"type":47,"items":60},[61,62,63,64,65,66],"**Multi-language OCR** via Tesseract: French, Arabic, Spanish, English and dozens of other languages configurable via environment variables","**Hierarchical tags**: fine-grained document organization with inherited automatic assignment rules","**Correspondents**: identification of recurring senders\u002Frecipients, automatic assignment by rule","**S3-compatible storage**: archive originals to an S3 or compatible bucket (MinIO, Garage) without modifying the interface","**Documented REST API**: integration with external workflows (n8n, curl scripts) via `\u002Fapi\u002Fdocuments\u002F`","**Consume folder**: any file dropped in `\u002Fconsume` is automatically ingested — natural connection for network scanners and mail clients",{"type":39,"body":68},"Papermerge v3 vs Paperless-ngx: comparison",{"type":70,"title":71,"headers":72,"rows":76},"comparison","Papermerge v3 vs Paperless-ngx",[73,74,75],"Criterion","Papermerge v3","Paperless-ngx",[77,81,85,89,93,97,101,105],[78,79,80],"Project status","Archiving announced ~Oct. 5, 2026","Active, regular releases",[82,83,84],"License","Apache 2.0","GPL-3.0",[86,87,88],"Backend","FastAPI (Python)","Django + Celery (Python)",[90,91,92],"OCR","Tesseract (manual configuration)","Tesseract multi-language, auto-detect",[94,95,96],"Document organization","Hierarchical folders","Tags, correspondents, document types",[98,99,100],"External storage","Not native","S3 \u002F S3-compatible (MinIO, Garage)",[102,103,104],"Official Docker Compose","Yes, but unmaintained after archiving","Yes, actively maintained",[106,107,108],"GitHub community","~2,500 stars","~23,000 stars",{"type":39,"body":110},"Prerequisites before migrating",{"type":42,"body":112},"Paperless-ngx is lighter than its reputation suggests. The minimum requirements for a team of 1 to 10 users with a corpus of a few thousand documents are reasonable on a standard VPS.",{"type":47,"items":114},[115,116,117,118,119,120],"**VPS: 2 vCPU \u002F 2 GB RAM minimum** — 4 GB recommended if OCR runs in parallel on multiple documents during ingestion","**Docker and Docker Compose**: Docker ≥ 24, Docker Compose ≥ 2.20 (integrated plugin, not the legacy Python binary)","**40 GB SSD storage minimum** for originals + index data; plan for more depending on archive volume","**Domain or subdomain** with a valid TLS certificate — Paperless-ngx does not require HTTPS but strongly recommends it for sessions and API tokens","**Root or sudo access** on the VPS to install Docker and configure the reverse proxy","**Backup of your existing Papermerge instance** before any operation: document export + database dump",{"type":39,"body":122},"Step-by-step migration guide",{"type":124,"title":15,"steps":125},"steps",[126,129,132,135,138,141,144,147],{"title":127,"body":128},"Export your documents from Papermerge","In the Papermerge interface, go to **Documents → Export**. Select \"All documents\" and start the export. Papermerge generates a ZIP file containing the originals (PDFs, images) organized by folder. Download this file to your local machine or transfer it directly to the target VPS via `scp`:\n```bash\nscp papermerge-export.zip user@your-vps:\u002Ftmp\u002F\n```",{"title":130,"body":131},"Unzip the export and prepare the consume folder","On the VPS, unzip the archive into a temporary directory:\n```bash\nmkdir -p \u002Fopt\u002Fpaperless-import\nunzip \u002Ftmp\u002Fpapermerge-export.zip -d \u002Fopt\u002Fpaperless-import\u002F\n```\nYou get a directory tree of files. Paperless-ngx will consume these files via its consume folder in a later step.",{"title":133,"body":134},"Install Paperless-ngx via the official Docker Compose file","Fetch the official `docker-compose.yml` from the Paperless-ngx repository:\n```bash\nmkdir -p \u002Fopt\u002Fpaperless && cd \u002Fopt\u002Fpaperless\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fpaperless-ngx\u002Fpaperless-ngx\u002Fmain\u002Fdocker\u002Fcompose\u002Fdocker-compose.postgres.yml -o docker-compose.yml\ncurl -fsSL https:\u002F\u002Fraw.githubusercontent.com\u002Fpaperless-ngx\u002Fpaperless-ngx\u002F.env.example -o .env\n```\nEdit the `.env` file: set `PAPERLESS_URL`, `PAPERLESS_SECRET_KEY` (a long random string), `PAPERLESS_OCR_LANGUAGE` (e.g. `fra+eng` for French + English), and `PAPERLESS_TIME_ZONE` (`Europe\u002FParis` or your timezone).",{"title":136,"body":137},"Start the instance and create the administrator account","Launch the containers in the background:\n```bash\ndocker compose up -d\n```\nWait for the service to be ready (30 to 60 seconds), then create the superuser:\n```bash\ndocker compose exec webserver python3 manage.py createsuperuser\n```\nLog in at `http:\u002F\u002Flocalhost:8000` (or your domain) to verify the interface responds.",{"title":139,"body":140},"Import documents exported from Papermerge","Copy the exported directory tree into the Paperless-ngx consume folder. By default, this folder is the `consume` volume declared in `docker-compose.yml`:\n```bash\ncp -r \u002Fopt\u002Fpaperless-import\u002F* \u002Fopt\u002Fpaperless\u002Fconsume\u002F\n```\nPaperless-ngx will automatically detect the new files and ingest them via Celery. You can monitor progress in the **Logs** tab of the interface or via:\n```bash\ndocker compose logs -f celeryworker\n```",{"title":142,"body":143},"Configure the reverse proxy and TLS","Expose Paperless-ngx behind nginx. Minimal block example for a subdomain:\n```bash\nserver {\n    listen 443 ssl;\n    server_name docs.your-domain.com;\n    ssl_certificate \u002Fetc\u002Fletsencrypt\u002Flive\u002Fdocs.your-domain.com\u002Ffullchain.pem;\n    ssl_certificate_key \u002Fetc\u002Fletsencrypt\u002Flive\u002Fdocs.your-domain.com\u002Fprivkey.pem;\n    location \u002F {\n        proxy_pass http:\u002F\u002F127.0.0.1:8000;\n        proxy_set_header Host $host;\n        proxy_set_header X-Real-IP $remote_addr;\n    }\n}\n```\nObtain or renew a Let's Encrypt certificate for this subdomain, then reload nginx.",{"title":145,"body":146},"Verify OCR coverage and test imported documents","In the Paperless-ngx interface, open several imported documents and verify their content is indexed (working search bar). For documents where OCR failed (warning icon), relaunch OCR manually from the interface or via the REST API:\n```bash\ncurl -X POST http:\u002F\u002Flocalhost:8000\u002Fapi\u002Fdocuments\u002F\u003Cid>\u002Fredo_ocr\u002F \\\n  -H 'Authorization: Token \u003Cyour-token>'\n```",{"title":148,"body":149},"Validate and shut down the old Papermerge instance","After the full import, verify that the document count in Paperless-ngx matches your Papermerge export. Test full-text search on known terms, check attachments and downloadable originals. Once validation is complete, stop the Papermerge instance and remove its containers: `docker compose down` from its deployment directory.",{"type":39,"body":151},"Essential Paperless-ngx configuration",{"type":42,"body":153},"After the initial import, three configuration areas have a direct impact on day-to-day service quality.",{"type":47,"items":155},[156,157,158,159],"**OCR**: `PAPERLESS_OCR_LANGUAGE` accepts a list of Tesseract language codes separated by `+` (`fra+eng+ara`). If your corpus is multilingual, declare all languages from the start so imported documents are reprocessed correctly","**S3 storage**: set `PAPERLESS_STORAGE_BACKEND=s3`, `PAPERLESS_S3_ACCESS_KEY`, `PAPERLESS_S3_SECRET_KEY` and `PAPERLESS_S3_BUCKET_NAME` to offload originals to an S3-compatible bucket — useful for multi-gigabyte corpora on a storage-limited VPS","**Automatic assignment rules**: in the interface, create rules that assign a tag, correspondent, or document type based on OCR content (e.g. any document containing \"invoice\" → tag `Invoices`, correspondent `Supplier X`)","**Scheduled tasks**: the Celery worker already handles automatic consumption; verify that `PAPERLESS_CONSUMER_POLLING` is `0` (inotify) or a reasonable interval if inotify is not available in your Docker environment",{"type":161,"body":162},"tip","To reduce ingestion time on a large corpus, enable parallel consumption by setting `PAPERLESS_TASK_WORKERS=4` in your `.env` (adjust to your vCPU count). On a 4 vCPU \u002F 4 GB RAM VPS, ingesting 500 single-page PDFs drops from ~20 min to ~6 min. Monitor memory: Tesseract consumes ~200 MB per active worker.",{"type":39,"body":164},"Integration with your existing tools",{"type":42,"body":166},"Paperless-ngx integrates into document workflows without custom development. Three entry points cover the majority of SME use cases.",{"type":47,"items":168},[169,170,171,172],"**Network scanner**: configure your scanner to send scans via SFTP or SMB into `\u002Fconsume`. Paperless-ngx ingests them on arrival, with no manual action required","**Mail client**: the mail consumer (`PAPERLESS_EMAIL_HOST`, `PAPERLESS_EMAIL_PORT`) monitors an IMAP mailbox and automatically imports PDF attachments from messages matching your filters (subject, sender)","**REST API**: the `POST \u002Fapi\u002Fdocuments\u002Fpost_document\u002F` endpoint accepts a multipart file. From n8n, a workflow can send any received email attachment directly to Paperless within seconds. The API token is generated under `Settings → API Tokens`","**Mobile app**: the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fastubenbord\u002Fpaperless-mobile\">Paperless Mobile\u003C\u002Fa> app (Android\u002FiOS, open source) connects to your self-hosted instance via URL and API token",{"type":39,"body":174},"Troubleshooting: common issues after migration",{"type":47,"items":176},[177,178,179,180],"**Imported documents with no OCR text**: verify the Tesseract language code is correct (`PAPERLESS_OCR_LANGUAGE=fra` not `fr`). Valid codes are listed in the \u003Ca href=\"https:\u002F\u002Ftesseract-ocr.github.io\u002Ftessdoc\u002FData-Files-in-different-versions.html\">Tesseract documentation\u003C\u002Fa>. Relaunch OCR on affected documents via the interface or API","**Consume folder not monitored**: if you use a Docker volume mounted from an NFS partition or object storage, inotify does not work. Set `PAPERLESS_CONSUMER_POLLING=60` for a scan every 60 seconds","**\"Permission denied\" error on `\u002Fconsume`**: the Paperless worker runs as UID 1000. If files copied to `\u002Fconsume` belong to root, change permissions: `chown -R 1000:1000 \u002Fopt\u002Fpaperless\u002Fconsume\u002F` on the host","**Incomplete import — missing documents**: Papermerge exports documents in the folder structure visible in its interface. Documents in deeply nested folders are all exported, but filenames containing special characters may cause issues. Check with `find \u002Fopt\u002Fpaperless-import -name '*.pdf' | wc -l` and compare to your Papermerge instance total",{"type":39,"body":182},"Take back control of your archives",{"type":42,"body":184},"The window is short: the papermerge-core repository will be archived around October 5, 2026 if no maintainer comes forward. Staying on a frozen Papermerge instance means silently accumulating a security debt on a tool that handles potentially sensitive documents — invoices, contracts, official correspondence.\n\nPaperless-ngx offers a lossless migration: your original files are imported as-is via the consume folder, OCR is rerun on documents that need it, and no destructive transformation is applied. The official Docker Compose deployment makes the installation reproducible in under an hour on any VPS. On ServOrbit, Paperless-ngx is available directly in the collaboration marketplace — you start from a pre-configured Docker Compose environment ready to receive your archives.","Deploy Paperless-ngx on your VPS","Papermerge is switching to a paid SaaS. Keep control of your document archives on a ServOrbit VPS with Paperless-ngx — GPL-3.0, ~23,000 GitHub stars, official Docker Compose. Installation in under an hour, data hosted on your own infrastructure.","Deploy Paperless-ngx","\u002Fmarketplace\u002Fcollaboration-productivity\u002Fpaperless-ngx",[190,208,228,244],{"id":191,"slug":192,"slugs":193,"title":197,"excerpt":198,"readTime":199,"views":200,"isPinned":19,"publishedAt":201,"updatedAt":202,"category":203,"categories":204,"featuredImage":30,"bgImage":31,"posterImage":206,"relatedSolution":207},85,"host-paperless-ngx-on-your-own-vps",{"fr":194,"en":192,"ar":195,"es":196},"heberger-paperless-ngx","استضافة-paperless-ngx-على-خادمك-الافتراضي-الخاص-vps","alojar-paperless-ngx-en-un-vps","Host Paperless-ngx on Your Own VPS: Complete Guide 2026","Install Paperless-ngx on a VPS: Docker Compose, multilingual OCR, 2.x→3.x migration, Redis\u002FValkey incompatibility and automatic backup. Updated guide.",17,1,"2026-03-27T00:00:00+00:00","2026-09-08T02:42:11+00:00",{"id":23,"name":24,"slug":25,"color":26,"icon":27},[205],{"id":23,"name":24,"slug":25,"color":26,"icon":27},"\u002Fblog\u002Fcovers\u002Fheberger-paperless-ngx-poster.svg",{"categorySlug":25,"appSlug":35},{"id":209,"slug":210,"slugs":211,"title":215,"excerpt":216,"readTime":217,"views":18,"isPinned":19,"publishedAt":218,"updatedAt":219,"category":220,"categories":225,"featuredImage":30,"bgImage":31,"posterImage":227,"relatedSolution":30},374,"saas-vs-self-hosted-real-cost-comparison-2026",{"fr":212,"en":210,"ar":213,"es":214},"saas-vs-self-hosted-comparatif-cout-2026","saas-مقابل-الاستضافة-الذاتية-مقارنة-التكاليف-2026","saas-vs-self-hosted-comparativa-de-costes-2026","SaaS vs self-hosted: real cost comparison 2026","Calculate the true TCO of 7 agency SaaS tools versus their self-hosted VPS equivalent. Is the switch worth the ~$14,000\u002Fyear in savings?",11,"2026-09-24T00:00:00+00:00","2026-09-24T12:27:51+00:00",{"id":221,"name":222,"slug":223,"color":224,"icon":223},5,"Comparison","comparatif","bg-info\u002F10 text-info",[226],{"id":221,"name":222,"slug":223,"color":224,"icon":223},"\u002Fblog\u002Fcovers\u002Fsaas-vs-self-hosted-comparatif-cout-2026-poster.svg",{"id":229,"slug":230,"slugs":231,"title":235,"excerpt":236,"readTime":237,"views":200,"isPinned":19,"publishedAt":238,"updatedAt":239,"category":240,"categories":241,"featuredImage":30,"bgImage":31,"posterImage":243,"relatedSolution":30},219,"bsl-and-sspl-the-traps-of-source-available-licenses",{"fr":232,"en":230,"ar":233,"es":234},"bsl-sspl-licences-self-hosting","bsl-وsspl-مخاطر-تراخيص-المصدر-المتاح","bsl-y-sspl-trampas-licencias-source-available","BSL and SSPL: the traps of source-available licenses","BSL, SSPL, AGPLv3: understand what each license allows or forbids before adding a tool to your stack.",12,"2026-08-04T00:00:00+00:00","2026-09-07T11:26:10+00:00",{"id":221,"name":222,"slug":223,"color":224,"icon":223},[242],{"id":221,"name":222,"slug":223,"color":224,"icon":223},"\u002Fblog\u002Fcovers\u002Fbsl-sspl-licences-self-hosting-poster.svg",{"id":245,"slug":246,"slugs":247,"title":251,"excerpt":252,"readTime":253,"views":18,"isPinned":19,"publishedAt":254,"updatedAt":255,"category":256,"categories":257,"featuredImage":30,"bgImage":31,"posterImage":259,"relatedSolution":260},342,"notion-2026-price-increase-docmost-self-hosted",{"fr":248,"en":246,"ar":249,"es":250},"notion-hausse-tarifaire-docmost-self-hosted","notion-2026-ziyadat-assaar-docmost-self-hosted","notion-2026-aumento-precios-docmost-self-hosted","Notion 2026 price hike: migrating to self-hosted Docmost","Notion bundled AI into its Business plan in 2026 with a price increase. Is Docmost (AGPL-3.0) a viable self-hosted alternative for agencies?",9,"2026-09-09T00:00:00+00:00","2026-09-09T21:41:07+00:00",{"id":221,"name":222,"slug":223,"color":224,"icon":223},[258],{"id":221,"name":222,"slug":223,"color":224,"icon":223},"\u002Fblog\u002Fcovers\u002Fnotion-hausse-tarifaire-docmost-self-hosted-poster.svg",{"categorySlug":34,"appSlug":261},"docmost",1790385798097]