Insights

Making migration work for accountancy solutions

Data flowing through a network

Growth, change, new requirements and solutions’ expanded capabilities can create a compelling case for changing accountancy software, but for a successful migration, you need to understand where you’re starting from.

Accountancy software is always evolving. Many organisations have already gone through at least one migration, shifting from desktop systems to the cloud. Mergers and acquisitions, separations, restructuring and new business requirements have prompted many others.

Increasingly, the capabilities of modern solutions, enhanced by AI, are an additional draw, leading to growing interest and activity in the market. For those struggling with the constraints of existing systems, there is often a strong business case, with the potential to unlock new efficiencies, automation and insights.

But businesses must look before they leap. It is easy to underestimate the work involved. Failures to accurately define the scope of work, access requirements and time required can derail migration projects, leading to delays and increasing costs – and potentially frustrating the migration goals.

Planning so you can avoid pitfalls is essential and can be easier with a migration partner to assist.

You need to know what you’re moving before embarking on the project.
Fallback Author David Stiff
Associate Director S&W

Scale and timing: Defining the migration project

Some of the questions organsiations need to consider are obvious, but also vital.

“What information you need to migrate is among the most basic questions, but it requires a clear answer,” says David Stiff, an Associate Director in S&W business outsourcing services.

That might be just moving year-end closing balance figures for each year or a full transactional history. In a recent case Stiff worked on, the client required migration of all transactions over the previous six years. The company initially estimated there would be about 30,000. There ended up being over 200,000 transactions.

“You need to know what you’re moving before embarking on the project,” Stiff adds.

That’s not least because it will have a direct impact on migration timelines. Businesses should give themselves plenty of space to avoid overruns and to prevent looming deadlines taking teams away from business priorities.

Accurately defining the scope at the outset will also reduce the risks of later changes that can complicate and extend migration projects unnecessarily. The discussions can clarify requirements early on and reveal any issues with the chosen solution.

The company migrating transactions, for example, was moving from NetSuite to Xero and had also been using the former as its approval system. The latter doesn’t offer this as a stand-alone option, so the project required a third-party application add-on, increasing the complexity and time required.

“It all starts with knowing as a business what you want to achieve and understanding what your chosen system can provide,” says Stiff.

The initial issue is often failing to understand the system you’re moving away from,
Fallback Author David Stiff
Associate Director S&W

Expectations and understanding

Crucially, it also demonstrates that a comprehensive understanding of the existing system, data and workflows is key. This is where many migrations can run into trouble.

In the example above, the existing figures were all in US dollars, reflecting the group from which the business separated. What the client had considered a simple migration from one system to the other, in fact required setting up the new system in the same currency to shift the data across and then converting into Sterling and reconciling the data.

“The initial issue is often failing to understand the system you’re moving away from,” says Stiff. “You need to know the data, the system’s capabilities, limitations and workflows, the approval processes, reporting requirements and integrations. They define what you’ll need your new solution to be able to do.”

None of which is an argument against migration. Increasing capabilities, such as the ability to link up with third-party packages like Expensify to automate processes and eliminate manual work and rekeying is valuable. But without an accurate estimation of the existing problems, realistic opportunities of migration and the challenges involved in the project to realise them, it is impossible to evaluate the likely return on investment.

“You need to do that first, before you make the decision,” says Stiff.

Because, when choosing a destination, it’s a good idea to know where you’re starting from.

Talk to us

Discuss your migration with our accounting software experts