When moving to Alfresco, many clients struggle with the cost and effort associated with a “Big-Bang” migration from their Legacy ECM system. In a “Big-Bang” scenario, all the content must be migrated to the new system during a very risky and expensive cutover weekend. Continue reading
As we’ve mentioned in a previous blog post, we often meet with potential clients who are interested in using OpenMigrate to meet a migration need but they haven’t yet identified specific migration requirements beyond the need to move documents from one location to another. It is important to identify requirements and an overall migration strategy as early as possible as migrations provide a great opportunity to “clean up” content management systems. This “cleansing” can be through object model updates, metadata cleansing, deletion or archival of obsolete documents, or other business related decisions.
Recently, we have seen an uptick in the number of requests for OpenMigrate support for migrating from Documentum to either another Documentum repository or a new repository like Alfresco or M-Files. Many times clients will opt to use a vendor supplied bulk upload tool as part of the migration and use OpenMigrate simply to dump the files from Documentum to a file system. This “two-step” approach doesn’t leverage the full ability of OpenMigrate to complete the migration in one step. For this post, we will discuss benefits of the one step approach as well as issues with typical bulk load utilities.
We recently discussed the concept of a rolling migration versus a more traditional big-bang migration approach. See our initial thoughts on development of a rolling migration approach for the eventual retirement of a client’s old system over time. After working through some of the challenges, we now have a system that can quickly move content into the new repository on demand. This post will discuss our results.
As summarized in our series of migration posts, many of our clients are moving to Alfresco from legacy ECM solutions. For one of our current clients, we are moving from an onsite Canon ImageWare solution to Alfresco hosted within the Amazon Cloud. This post will share our experience migrating from ImageWare to Alfresco and include some specifics in regards to technical migration nuances. Continue reading
One of the biggest challenges in rolling out new interfaces for ECM is migration from older/legacy systems. We just started working with one financial services client that, in moving toward an Alfresco and HPI 2.1 solution, has initiated a hybrid approach to allow the interface to be introduced quickly while simplifying and reducing the risk of a large migration and big bang rollout. This post will detail the approach for reference and discussion. Continue reading
Last week, we put together an overview of migrations and OpenMigrate for one of our partners. The overview had a couple of interesting analogies regarding migrations as well as best practices that we will share in this post. Continue reading
Many experienced Documentum customers have attempted to leverage the Google appliance as an alternative to Documentum Search or as part of an Enterprise Search effort. One of our clients presented their experience at our user group meeting. This post will discuss their findings. Continue reading
As the developers of OpenMigrate, we are always amazed by how often a new tool is unveiled that claims to make migrations considerably easier. While we love what we have done with OpenMigrate, we also typically have to educate clients that a migration tool, just like other tools, is only part of the effort. This post will touch on all of the other requirements of a migration effort beyond just moving documents from point A to point B quickly.
Two weeks ago we completed several of the largest Documentum migrations and upgrades we’ve ever seen. With short outage windows, we helped plan and support our client’s migration of their Documentum systems from a data center in the southeast US to the Rockies while simultaneously upgrading the repositories from Documentum 6.5 to 6.7 SPx. Altogether the repositories contained over 2 billion documents, several TB of file server and multiple Centera devices; as well as over 425,000 ActiveWizard forms!