2017
15
February

Hard Truth: Atlassian Migrations are seldom easy

One of the most common questions I get from customers is: “so how much does a migration to Atlassian cost?” To which I deliver an uncomfortable response: “it’s complicated.”

Here’s the rub: No two migrations are alike… ever (you’ll see a galloping herd of unicorns before you have two identical migrations). Individual environments are chock full of unique complexities and nuances. Catching all blockers, hiccups, problems, unknowns, or whatever else you wish to call them is nearly impossible. Many customers know because they have tried to migrate on their own… and failed. This why you come to a Solutions Partner like Isos.

Unfortunately I don’t have a magic mirror in my back pocket which I can ask for the exact time and cost to move their data from point A to point B, all wrapped up in handy crib notes. There is no magic, only experience, and my experience has provided me with a major take away: migrations are always, always, always iterative.

Here are some major points which everyone involved should understand before starting a migration project:

  • Discovery, Discovery, Discovery:
    • We can discuss what specifics are thought to be on presales calls, but we never really know what’s under the hood until we get under the hood. Every project requires time to get familiar with environment details, application details, and time to create a migration path. Any project without discovery will have horrible surprises.
  • Dual Effort:
    • Both our teams need to work together to ensure the process is effective and complete. This means team discovery time, team consensus on process and execution, and team agreement on completion.
  • Iteration == Communication:
    • Tackling projects from an iterative perspective allows time for backlog grooming, reprioritizing of issues, fact checking, and knowledge transfer.

Understanding these points is the first step to successful migration projects. The next step is to make sure each iteration is more successful than the last. Stay tuned for my next blog post around how to ensure productivity is prevalent in every iteration!

Share with your peeps...Share on FacebookShare on Google+Tweet about this on TwitterShare on LinkedIn
Tagged with: , , — Posted in Atlassian

Leave a Reply