2012 – 2013: When Data Became Something to Understand
By the end of 2011, the Cloud had quietly become part of the everyday business infrastructure.
Companies were no longer debating whether to adopt it; they were already using it, often without thinking too much about it. Email was hosted, files were synchronised, and applications were increasingly delivered through the browser. Just as importantly, expectations had shifted. Systems were assumed to be available everywhere, all the time.
But alongside that normalisation came a new realisation. If data was now centralised, accessible, and effectively limitless in terms of storage, it was no longer just something to keep. It was something to use. That idea – hinted at in the previous phase – began to take shape in 2012, and it immediately exposed a problem. Most organisations didn’t really understand the data they had.
The Infrastructure Was Ready
The infrastructure was ready. Platforms from companies like Microsoft and Amazon Web Services were stable and growing rapidly, while services such as Office 365 were gaining real traction. From a technical perspective, there were fewer and fewer barriers to moving workloads into the Cloud. The challenge had shifted. It was no longer about where systems ran, but understanding what was actually being moved.
This became particularly clear when organisations looked at their existing data estates. Years of accumulated information: emails, archives, shared drives, and backups had grown in ways that were rarely structured or well understood. Among the most problematic of these were PST files: scattered, duplicated, often unmanaged, and yet full of business-critical history. They represented exactly the kind of data that companies now wanted to analyse, retain, or migrate. And yet they were also among the least visible.
A World That Expected Immediacy
At the same time, the wider world was demonstrating just how important fast, accessible data had become. The London 2012 Olympic Games offered a vivid example. For the first time, a global event of that scale was experienced not just through scheduled broadcasts, but in real time across smartphones, apps, and social platforms. Updates flowed instantly, results were tracked live, and conversations unfolded moment by moment on services like Twitter. Behind that experience was infrastructure capable of scaling on demand and processing vast volumes of information in real time. Precisely the kind of capability the Cloud had been building towards.
For businesses this wasn’t just impressive – it was instructive. It showed what users now expected: immediacy, reliability, and access from anywhere. But delivering that kind of experience internally required more than just adopting Cloud platforms. It required clarity about the data itself.
The Problem Nobody Had Fully Faced
This is where 2012 marked a genuine turning point. The focus began to move away from simply transferring data and towards understanding it before taking action. Tools emerged that reflected this shift, including Transvault’s PST Insight, released in early 2012. Rather than treating PST files as opaque containers to be moved wholesale, it allowed organisations to locate them wherever they were hidden, and examine their contents in detail – identifying age, ownership, duplication, and relevance.
Seeing What You Actually Had
That seemingly simple capability had a significant impact. For the first time, companies could approach migration selectively. Instead of carrying everything forward by default, organisations could decide what actually mattered. In many cases, this led to substantial reductions in data volumes, but more importantly, it introduced a different mindset. Data was no longer just something to preserve; it was something to evaluate.
From Technical Exercise to Strategic Decision
As that mindset took hold, the nature of migration began to change. What had once been a largely technical exercise (moving systems from one place to another) became more strategic. Decisions increasingly involved questions of risk, compliance, and business value. Organisations needed to understand not just what they had, but why they had it, how long it should be retained, and what obligations were attached to it.
Data Everywhere, By Default
At the same time, the broader technology landscape continued to reinforce these shifts. Services like Google Drive, launched in 2012, made Cloud-based storage feel entirely normal to everyday users. New applications were designed to live in the Cloud from the outset, and new companies were built without ever owning physical infrastructure. The distinction between “local” and “remote” computing continued to blur.
The Weight of Responsibility
With this came increasing responsibility. As data became more central to operations, it also became more regulated. Organisations were expected to demonstrate control: to show where information was stored, who could access it, and how it had been handled over time. This added another layer of complexity to migration efforts, reinforcing the need for accuracy, traceability, and completeness.
A Different Kind of Progress
By 2013, it was clear that success in this new environment depended less on speed and more on understanding. The organisations that navigated the transition most effectively were those that took the time to analyse their data before moving it, reducing unnecessary volume and addressing risks early. They treated data as something to be managed deliberately, rather than accumulated by default.
Looking back, this period doesn’t stand out because of a single defining innovation. Instead, it represents a shift in perspective. The Cloud had made it possible to store and access almost unlimited amounts of information. The challenge, and increasingly the opportunity, lay in making sense of it.
What Understanding Made Possible
And that set the stage for what came next. Once organisations understood their data – what it contained, what it meant, and what it was worth – the next question was no longer about insight, but execution. How to move it efficiently, repeatedly, and at scale would become the defining challenge of the following phase. At the same time, growing internal ownership and an increasingly varied migration requirements created a demand for far greater flexibility, a subject which we’ll talk about in the next article.
