Skip to content
Data & IT: legacy data, formats, connectorsElectronics & SensorsMachinery & Plant EngineeringEnergy & UtilitiesChemicals & Process Industry+2

From file share to cloud, with clean permissions

You move from the file server to the cloud without copying old rights blindly, and demi checks every share afterwards.

Today

When moving from the file server to the cloud, old rights are either copied blindly or lost, and both go wrong. Over the years, shares open to everyone, one-off permissions and accounts of people long gone have piled up. Taking them along takes the mess along, and later the AI in the new storage finds exactly what nobody should see.

An example

Wallner+Hardt Sensortechnik is moving 4.2 TB from its file server to the cloud. demi finds 312 folders anyone in the company can open, including the development files of a customer project under NDA, and 47 leavers' accounts with valid rights. The area heads approve 18 libraries with 26 roles, and the check after the move shows that nobody sees more than approved.
Fictional company, typical workflow.

Your data, wherever it lives

Today your data sits on file servers and NAS boxes, in folders with rights grown over the years, as Word and spreadsheet files, PDFs and drawings; the accounts live in the directory, the leavers in the HR system. demi reads, understands and links folders, rights, groups and the org chart, with your rights. The AI proposes libraries and roles for SharePoint and Teams in days and checks every share after the move, and the owners of each area decide.

Where the data lives today

  • Folders & drives
  • NAS & hard disks
  • SharePoint
  • Office files
  • PDFs
  • HR system
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from file servers, NAS, the directory, the HR system and the new storage. demi replaces nothing and builds, per folder, a picture of effective rights, use and owner. demi sets rights in the new storage only after approval.

  2. 2 · PermitPermission Layer

    This is the Permission Layer at work: rights follow role and org chart, not a folder's history. Each area has an owner who approves structure and roles, and nobody gets more access than approved. Every change is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads effective rights exactly, including nested groups and inheritance, and matches accounts against leavers. From the org chart and actual use it derives libraries and roles and flags paths that will be too long and characters the new storage does not accept. After the move it compares target and actual.

How it runs

  1. 1

    demi reads folders, effective rights, groups and accounts from the file server, NAS and directory.

  2. 2

    The agent finds shares open to everyone, leavers' accounts, one-off permissions and paths that will be too long.

  3. 3

    It proposes libraries, channels and roles, derived from the org chart and actual use.

  4. 4

    The owners of each area check and approve structure and rights.

  5. 5

    After the move demi checks the rights against the plan and reports every deviation.

What changes

  • No blind copying of old rights

  • Nobody sees more than approved after the move

  • Clean rights before AI searches the new storage

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+180 hfreed per year

Assumptions and calculation

demi reads the old rights, proposes roles for the new storage and checks after the move; you approve.

15 min → 9 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

150 folders with own permissions × 15 min × 40% × 1.0 (manual) × 12 months = 10,800 min = 180 h

Value per year, before demi costs

Freed per year+180 h

Assumption: labour cost of €49.50 per hour in German manufacturing in 2025 (Destatis), plus workplace, IT and overheads.

= Value per year, before demi costs

+€11,700

gained per year

180 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Does demi simply carry over the old folder rights?

No. demi reads them exactly, with groups and inheritance, and shows where they are too broad or outdated. That becomes a proposal for roles, which the owners of each area approve. Only what is approved is carried over.

Does demi do the move itself?

demi plans and checks. The move can be done by your migration tool or by demi itself, in stages after approval. Before each stage demi shows what moves and who may see it afterwards, and after it comes the check against the plan.

Why do clean rights matter so much before using AI?

An AI assistant finds everything the person it works for may see. If a folder is open to everyone, its content ends up in answers to everyone. Clean up before the move and you can switch on AI in the new storage without nasty surprises.

Does data nobody needs move too?

Not automatically. What nobody has opened in years, demi proposes for the archive instead of moving it. The owner decides, and retention periods are kept.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases