Content Migration
Moving data from one location to another, from one system of record to another or onboarding a new business process can all generate common pain points and concerns.
In our experience, our customers migrate from one primary system of record to another for 3 primary reasons.
- The cost of the current system has grown out of budget. Costs of version upgrades by major solution providers, coupled with the cost of annual maintenance and the man-hour costs of managing an upgrade become risky. These budget decisions alone make organizations reconsider their renewal decisions.
- Loss of support. Software manufacturers may decide to drop a specific feature that is the one key benefit to your organization. Feature changes, depreciation or drop is a quite but common occurrence (check out the list of “depreciated” features in Oracle 12c https://bit.ly/2lOQKE1). When the cost of maintenance, a major upgrade, and man-hours are under consideration it is especially painful to accept paying more for what your organization perceives as less.
- Big Data Problems. This may sound like a business problem Netflix or Amazon has, but consider how many places and individuals save and share the same document within your organization. This may be trivial storage cost, but it is a great big compliance and security risk. It also seems to be one of the first indications that a department or business problem is being partially automated, and could benefit from a more thoughtful migration to your system of record or platform of choice. If data is being stored, shared or extended through multiple locations (think desktop, email, back up to share, FTP, repository, cloud, Dropbox/Box) you may have a big problem. Multiple content locations make corporate/organizational policies, security practices and even regulations easy to ignore.
