While COVID-19 continues to cause devastating disruption to the global economy more than two years into the pandemic, it is also continuing to force remarkable innovation across different industries. Companies have found new ways to sell, service and operate during the crisis. For me, there is one common theme for these innovative companies, including Qlik, and it is “Jobs to be Done.”
In an era where the passage of time seems to have changed somehow, it definitely feels strange to already be reflecting on another year gone by. It’s a cliche for a reason–the world definitely feels like it’s moving faster than ever, and in some completely unexpected directions. Sometimes it feels like we’re living in a time lapse when I consider the pace of technological progress I’ve witnessed in just a year.
Since I’m now migrating NodeGraph’s processes to Qlik, I thought it may be a good time to talk about migrating data during a merger or acquisition. There are many aspects to consider. Here are some of my thoughts on why companies merge or migrate data landscapes, common M&A migration pitfalls and how to avoid them, the time and cost involved migrating data during a merger or acquisition, and other topics.