Migration
The switch is a day, not a project.
Most SMEs don't start from scratch — they have a running QMS in Word, PDF or Confluence. easo has a path in: adopt everything on day one, then convert into living documents step by step. Honestly, limits included.
You don't start from scratch
A switch rarely fails on the software — it fails on the fear of switching itself: "we'd have to redo everything." Not with easo. Your existing documents come in unchanged, and your QMS is in easo from day one — with an honest readiness picture instead of an empty system.
Two ways in
-
Adopt as-is
Any file type (up to 25 MB): easo creates a controlled document and pins the byte-exact original as an attachment — tamper-evident, versioned and immediately releasable with a signature. Provenance and a legacy ID are preserved.
-
Convert to draft
.docx, HTML, Markdown and text become a canonical easo draft — behind a review-before-release gate. Conversion loss is reported loudly per file; embedded images go into the same signed record.
Day one: adopt everything
Start cheap: adopt your whole document set "as-is" and clause-link the documents to ISO 9001. Now your QMS is in easo and shows an honest readiness score — what's there, what's missing, where you stand. No big bang, no empty system to laboriously fill first.
Then: step by step to living documents
Whenever you'd touch a document anyway, convert it into a living easo document. The new document supersedes the original — which stays marked and inspectable forever (ISO 9001 §7.5.3). So your QMS grows at your pace, not in a risky cut-over weekend. Migration is a process, not an event.
Honestly framed
We promise no magic. easo deliberately doesn't extract text from PDFs (no OCR — fidelity on real-world QMS PDFs would be dishonest); adopt those files as-is. There are no connectors to SharePoint, Confluence or other QMS tools — they export to files, and you import those. And imported content is never released blindly: the review stays with a human. Your documents live in your own Git throughout — the way in is also the way back out.
Common questions about switching
Do I have to rebuild my existing QMS?
No. You adopt your existing documents as-is on day one. From then on your QMS runs in easo — and you convert documents into living easo documents at your own pace, whenever you're working on the content anyway.
Can I import Word documents?
Yes. easo converts .docx, HTML, Markdown and plain text into an easo draft — behind a review-before-release gate. Conversion loss is reported loudly per file; nothing is silently swallowed.
What happens to my PDFs?
You adopt PDFs as-is: easo creates a controlled document and pins the byte-exact original as an attachment. We deliberately don't extract text from PDFs and use no OCR — fidelity on real-world QMS PDFs would be dishonest.
How long does the switch really take?
The switch itself is a day: adopt everything, clause-link it, done — your QMS is in easo and shows an honest readiness picture from day one. Converting into living documents is a process after that, not an event, and runs at your own pace.
Is there a connector for SharePoint or Confluence?
No, deliberately not. Each of those systems can export to files, and you import those files into easo. That covers every source without fragile interfaces to third-party APIs.
Are my originals altered?
Never. The original is pinned byte-exact and retained. If you convert it later, the new document supersedes the original — the superseded one stays marked and inspectable forever.
Stay in the loop
easo is available for macOS — the Windows version is coming soon. Leave us a note and we'll reach out the moment it lands.