Full and easy control of the whole content-move or migration process
Full flexibility: the content migration can be done in batches, in smaller, better manageable units. The batches can be grouped by any attribute, e.g. create_date or object_type.
Actively manage and control the whole process. Start, stop and pause any time to keep the impact on the system as low as possible.
Individual error handling
Error handling is much easier. It is on an object basis and very well reported. For each batch run an error report will be created and is already visible during the process of the content move. This results in better information about the error objects to investigate into the matter.
Renditions, versions and checked-out
Parameters in the Importer (Updater) enable also the move of the content files for renditions and for all versions. No need to scan all objects in the repository: the object’s current version is enough.
Additionally checked-out documents can be moved as well. The user will simply not notice that the content was moved.
All the tasks can be executed in parallel. Scanning and moving/updating can be done with many jobs at the same time. Each job is also using up to 20 threads internally. Roughly 100.000 content files are scanned and moved in under an hour – with minimal setup (1 Jobserver).
Clean up, enrich or reorganize
Another advantage is to have the ability to do updates to the metadata as well. Sometimes it is purely needed to move content (e. g. because the storage system will be shut down) the fastest way but sometimes it is really helpful also to reclassify the existing process during that process.
Carry out two tasks with one tool!