Of course it works! We’ve been using it since the beginning, and it worked well all the time.
Planning to upgrade, consolidate or replace your ECM is not an easy task, but you must do it because of different reasons (reasons are not part of our topic today but maybe in a future post). After you create the concept and conduct the planning, you setup, configure and customize the new platform and finally you reach the point when you need to fill it with your data. Since most of the new platforms offer functionalities for bulk importing documents from a file share, one of the options you have is to manually export the content from one or multiple sources to a file share and after that import it to the new platform. Since you don’t have only a few documents, you start thinking how to split the work into smaller chunks so you can migrate the content gradually. You can do it folder by folder or library by library. So, it depends on the amount of data. You may finish the work after a few days but most probably after some weeks. But how will the end users deal with the content during this time, since some of the content is in the new system, while some is still in the old one?
Another important aspect when talking about content migration is the metadata of the objects. How can you manually migrate metadata? Well, if we are talking, for example, about migrating documents from Microsoft Sharepoint on-premises to Sharepoint Online, you can archive an entire document library and import it as it is in the destination so that the metadata will be preserved. But how can you set the metadata when migrating from a different legacy system? One option would be to create some scripts that will set the metadata after the content was copied to the target system. But this will introduce another layer of complexity, increasing the risk and reducing the predictability of the migration.
In most of the cases manual migration is not an option because:
- It is very time-consuming and error-prone due to the amount of manual work involved in the process
- Long running projects with interruptions of the daily business operations
- In most of the cases the development of scripts for restructuring the content and metadata is required, so the project becomes unpredictable in terms of costs and risks
- For a large amount of data, manual migration is simply not feasible