4 Top Reasons PST Migration Projects Fail
2. Migrating PSTs: Too much effort…..for what reward?
Although the technical benefits of getting rid of PSTs might be obvious to the IT manager, the payback of rounding up PSTs to the business might not be so apparent to ‘the board’, leaving a migration project low down in the pecking order of priorities.
The difficulty is that PSTs are like locked personal filing cabinets, which means the information risk they pose to the business is difficult to quantify and therefore easily ignored.
What you don’t know doesn’t hurt you, right?
It’s highly likely that your enterprise PSTs contain very little information that is of merit or interest to the company. A large percentage of content may be personal: jokes, junk mail, images and sound files, etc.
The prospect of uploading what is essentially rubbish into the corporate email system, a dedicated archive or perhaps even a hosted email service is anathema to many enterprises. Apart from consuming large amounts of storage, the process could take too long and cost too much.
On the flip side, PSTs may well constitute vital business records such as sensitive emails, contact lists, confidential reports, personal data, budgets and financial results. They may even contain content that would be relevant to an eDiscovery case or would be covered under GDPR legislation.
In fact, PSTs are a convenient way to covertly extract emails, contacts and calendar entries out of the corporate email system…arguably this in itself is good reason to want to get them under control.
You might want to check out this ‘life hacker’ article and in particular the replies to it, to understand some of the issues at stake when users start extracting emails into PST files.
The reality is that to get the business to focus on the PST issue, you need some way of quantifying the potential risk posed to the business by the content of PSTs. Only then can an informed decision be made and a project justified.