Consolidation Solutions

Problem: Disparate Tools/Processes

We’d all like to think that our employees are all working from the same products, processes, procedures, and platforms. In reality most big, really big, companies are just many small companies connected together.  Even the smallest of companies can become siloed with loosely connected products.  If we’re lucky, they’ll all be the same tool but how they’re used can vary from department to department. reinventing the wheel with different processes and procedures for the same job.

Because of this, Consolidation Solutions must consider more than just merging all the teams onto the same tools. For tools like Jira, Confluence, Bitbucket, Bamboo, Jenkins, etc. we need to consolidate and standardize things like workflows, automations, testing, etc. In standardizing this way, we can also take advantage of other benefits like fewer infrastructure resources, Single Sign-On, and Cross-Team resource utilization, saving money in the process.

Read our Use Case Stories below about the International companies who used different tools that couldn’t talk to each other and other companies whose departments reinvented the same wheel locally so many times, they had twice as many licenses than they had employees in the company!


Solution: Consolidation (Instances and Processes)

Sometimes having all your eggs in one basket is the best solution. Especially if that basket has redundancy, High Availability, and Standardized processes built in.

  1. Assess all the team to find all that use the same tool(s).
  2. Identify which instance has the most vetted and procedurally compliant processes (workflows, automations, notifications, etc.). This is your “one basket”.
  3. Identify those instances with the largest differences and least compliant processes and begin changes to bring them in line.
    These instances will take the longest to change, which is why you start them soonest.
  4. Modify processes in all other instances that are to be moved to the “one basket”.
    This step is often skipped, which means not only does this make migrating the data almost impossible, due to different custom fields, etc., but also requires its users to learn a new process over night.
  5. Plan and implement hardware and software upgrades necessary to support the migration/consolidation.
  6. As each instance comes into compliance begin test migrations of their data to Sandbox instances and perform verification/UAT testing.
  7. Schedule and execute each instance migration. When your employees come into work on Monday, they just log into a new server and pick up where they left off Friday.

Use Cases

Stories from the front lines

Coming Soon!