Your documents currently sit on an old network drive, in Google Drive, SharePoint, a wiki, ... . We collect them, put them in the right place, and count afterwards to check everything is there. You see the complete plan before anything moves.
There are four versions of the same contract, and nobody knows which one is correct any more.
Half of it is on the network drive, the rest in mailboxes and on laptops.
Migrating is scary: if something disappears, you only notice months later.
That last one is the real reason it keeps getting postponed. It is exactly what we built this for.
Offiks.ai makes an inventory: how many documents, how old, what is duplicated, who has access where. No content is read — only names, dates, sizes and permissions. You get a report showing what is there.
Offiks.ai proposes which document goes where, and with which attributes. The plan first runs as a dry run: for each document you see where it would end up, without anything being moved. Only once you sign off does anything happen.
First the structure and the access rights, again with a trial run beforehand. Then Offiks.ai moves the documents themselves, in batches. Each document keeps a record of where it came from, so you can always trace it back.
At the end Offiks.ai does a count: this many left, this many arrived. If even one document is still outstanding or has failed, the answer is not “done”. Errors are not averaged away — they block sign-off until they are resolved.
Yes. This is not a weekend where everything grinds to a halt. During the migration, everyone simply keeps working in the old location. We keep track of what changes in the meantime. At the moment of switchover we only pick up those changes — a matter of minutes, not hours.
Then we pick up where it stopped. We track the progress of each document separately, so an interrupted migration does not start over and never delivers anything twice. Whatever failed stays visible until it is resolved.
The analysis runs on our consultant’s machine, not in a cloud. Nothing leaves except the documents that move according to your approved plan. The worklist with your file names is deleted afterwards.
Old versions can come along, in the right order, if you want — by default only the latest one moves. We read out access rights and translate them too. Where the system is unsure, a person decides: existing permissions are never simply overwritten.
The classic shared drive with years of history. We read out the folders and access rights exactly as they are.
This is the fastest route. Microsoft gives us a fingerprint per file, so we can count duplicates without opening the files themselves. Deleted documents are also properly included in the count.
For attachments in a wiki. We use Confluence labels as a starting point for attributes — but never automatically: you decide which ones are included.
The first step is an inventory of your current documents. It produces a report you can use even without us: how many documents, how old, how many duplicates, and what would stand in the way of a migration. After that, you decide whether to go further.
Request an inventory