Identify potential problems in advanceReduce migration costs by 50%

  1. Reduce the number of objects to migrate and their dependencies.
    • Reliably identify unused data to exclude it from migration.
    • You can also reliably identify unused permissions. This reduces the clarification effort during the migration.
  2. Let yourself through migRaven.one point out specific problems:
    • too long directory paths
    • not suitable file types
    • exceeding of capacity limits
  3. Package those Migration useful based on existing permissions.
  4. Manage it all Projects centrally via one platform.
  5. Work in a team: Coordination and organization directly with the data owner via an interface.
  6. Benefit from scalability: Proven in large migrations.

migRaven.one im Videos


migRaven.one Inquiry

Regardless of whether you have a general question, a price inquiry or a desired test:

«There is hardly a system in the IT landscape that is anchored as centrally as a file server»

Thomas Gomell, CEO of migRaven GmbH

With the help of comprehensive analyses, you can identify in advance, among other things, where mountains of obsolete data are located. goal of every migration migRaven.one is the sustainable simplification of data and authorization structures.

understand data

Step 1 - Analysis

Mountains of data in directories that are far too deep and outdated, chaotic authorization structures are carried out before the actual migration migRaven.one analyzed. This gives you a comprehensive overview of the environment to be migrated.

Step 2 - Clean Up

On average, 80% of all data and structures are completely outdated and thousands of folders don't even need to be migrated. The integrated task management of migRaven.one enables effective coordination with departments and data owners to make quick decisions on which directories to migrate, archive or delete.

What you should have "on the slip" of a file server migration

  • Data quality and integrity
  • Impact on business
  • Costs
  • Impact on user experience
  • Who can make binding decisions regarding the data? (data owner)
  • Links within files
  • Links to files (shortcuts)
  • Application directories

avoid errors

Dependencies which can generate nasty errors:

 

  1. Applications (control systems for machines, SAP, logging software, etc.) use directories on the file server and will fail if the paths on the file server change.
  2. Links from and to files will break if no appropriate precautions are taken.
  3. Users rely on their structure and that their data will still be in the same place tomorrow. They will seek data and do their job more slowly or not at all when that is no longer the case. And they will turn to IT for that.

 

move data

Step 3 - Design new target structure for file server migration

A clear basic structure is essential for a directory and authorization structure that can be used in the long term. Build with us migRaven.one one by department, exchange, project and process directories structured filing with few levels, the current claims both for ease of collaboration and for security and manageability.

Step 4 - Migrate the relevant (!) Directories

In the last step, all tasks and decisions together, the migRaven.one collected during the migration. Copy jobs, archiving processes and the assignment of access rights are time-controlled in order to completely implement the migration in the file system by your desired date.

The integrated task management of migRaven.one ensures a clear division of tasks and smooth coordination between IT and specialist departments during the migration phase. 

TOP