Understand the sources
We map files, metadata, versions and permissions. Together we decide what to move, what to clean up and what to leave in place.
Move your documents to a new DMS
Transfer the documents and data you need from an existing system or repository. We prepare data, run a trial migration and verify the result.
Map to the target system
We define naming, categories, owners and relationships. A trial migration exposes inconsistent data before the final transition.
Check results and exceptions
Validation covers content, counts and important document properties. Errors and exceptions are listed for resolution.
Help users make the switch
We plan final updates, access to older material and user communication. Migration of Czech eSSL also requires attention to registration and file relationships.
Inventory → Mapping and rules → Trial migration → Completeness checks → Controlled cutover → Handover and traceability. Conceptual diagram · not a fixed product configuration
Frequently asked questions
What moves during migration besides files?
Depending on the source, metadata, versions, folders, relationships and permissions may also be transferred. We agree scope and validation first. A trial shows which data need completing or correcting.
What matters most when replacing a records system?
Obtain data descriptions and exports early, map document and case relationships, and agree how open work will continue. Trial migration and result checks belong in the plan before the old system is retired.
How can we reduce vendor lock-in?
Agree export of documents, metadata and relationships, interface documentation and exit assistance. Test whether the export is usable. Being able to download files is not the same as transferring the whole solution.
Must every application go live at once?
No. A DMS can often start with one application. Statutory records management also needs continuity of registration and operation. Plan stages around those duties and dependencies, not just screens.
What affects implementation cost and timing?
Applications, users, interfaces, data quality and customisation all matter. A proposal should distinguish licences, implementation, migration and support. A useful schedule also accounts for the customer's preparation and participation.