The Apple iPad is only seven years old this year. Believe it or not, the first one was launched in April 2010, and if you dig a first generation iPad out of the storage cupboard you’ll find it’s probably more useful as a paperweight than anything else – it doesn’t even have a camera! Frighteningly it, and second and third generation iPads, are also unsupported by Apple.
Leaving aside Apple’s rabid upgrade tactics and the notoriously short lifespan of its devices, this is just one indication of how fast technology is changing. Therefore, it’s likely that the decision on whether or not to upgrade your financial system, for instance, is pretty much a done deal. Any argument for a “wait and see” approach has been crushed by the reality that the longer you stay with a legacy system, the further you fall behind your competitors, your customers and your employees.
In the event of a disaster your clapped out old iPad 1 equivalent is going to be harder and more expensive to fix, and the risk of data loss is greater. But you need to go into any systems migration with your eyes wide open. Here are some of the things to watch for.
End User Resistance
One of the main factors that can make the difference between a migration project sinking or swimming is the involvement of the end users. Consider the public outcry when a platform such as Facebook or Instagram makes even minor changes to their software.
End users are typically attached to familiar experiences of systems, and this colours their expectations of any upgrades. Plus, they expect systems to be as easy-to-use and intuitive as the consumer apps they use every day. A disconnect here can manifest as resistance to the new system and a loss of time and money for the business.
User Requirements It is also vital to understand your users’ requirements and deliver on that. In other words, give them what they need to do their jobs well; don’t give them everything merely because it is there in the new ERP system.
Learn from the Google search home page: limit complexity to improve productivity. Do users really need to enter account codes? And for that matter, do they even need to see them? Remember that what a non-financial user of your new system requires can be quite different to that of a finance department user.
Chart of Accounts Opportunity Now consider that a financial systems migration is a great opportunity to restructure your company’s chart of accounts (COA). Your business has almost definitely changed to such an extent that your current COA is no longer suitable to today’s reporting requirements.
However, when implementing an updated COA you need to get two things right. You need to create an environment whereby you can provide reasonable comparative information when the account codes are different. And, secondly, you need to figure out how to reproduce historical numbers when the accounts, as well as how they are aggregated, differ to the legacy system.
When mapping historical codes to new ones it is unlikely that there will be a one-to-one relationship from old to new. And when you have a one-to-many or many-to-one relationship, comparative reporting becomes a challenge.
Data Migration And what about data migration? Decisions need to be made about which data is migrated and how many years to go back. The simple decision is normally to migrate immediate history and maintain a minimum license on the old system to be able to access historical information. But do you really think your old system is going to be a key priority for your previous service provider, especially after you have slashed your contract with them?
Major system migration is never easy and the pitfalls are many, despite what the salesman tells you! However, if you approach challenges with eyes wide open you are better prepared to identify the potential pitfalls and navigate around them.
Article published on Accountingweb May 2017 http://www.accountingweb.co.uk/community/blogs/kevin-philips/fs-system-migrations-beware-the-pitfalls-and-enjoy-the-upsides