Choosing the route to Cloud


Jon Allen, Change8’s IT programme delivery director led the first IFS Cloud implementation in the UK. Jon has extensive experience implementing IFS in multi-site and multi-national organisations.

Choosing the route to Cloud

There are two routes to Cloud for existing IFS customers: technical uplift and re-implementation.

The move to IFS Cloud is a big business change. It requires investment in people as well as the financial cost of delivery, whichever route you choose.

The key factors driving the decision will be your business’ strategic goals and how well these can be supported by your current IFS.

There are opportunities, risks and costs to consider.A good digital partner will always recommend a review to establish the business case and value proposition of the IFS Cloud implementation.

Technical uplift or re-implementation?

Technical uplift


Benefits of technical uplift

  • Faster to go-live: it generally takes between six and nine months to go-live, depending on the complexity of the system and what data needs to be tested.
  • You’ll want to assess whether it’s a strict technical upgrade or if there is a need to reduce customisation and modifications.
  • Lower risk: there’s no need for data migration as all the data is uplifted to Cloud.
  • Historical reporting: You retain all the data so previous year analysis can be done.
  • Simpler: IFS performs the uplift
  • Cheaper in the short-term: consultant costs are lower ahead of go-live.

Challenges of technical uplift

  • Retention of data: the good and bad data will come into Cloud unless customers do a cleanse before the uplift. The biggest hurdle here is the financial set up, because all the modules feed into finance. If you have hundreds of thousands of transactions you’ll bring them all and get stuck with the existing financial structure.
  • More expensive and more effort in the long-term: you’ve brought all your bad data and bad habits with you. You still need to re-engineer your processes, introduce new functionality and make technical changes. You’ll do all of this after go-live.
  • Slower to realise the value the in the product: you have to have a period of system stability with no functional or technical changes after a fixed stage in the upgrade. Plus, there’s no opportunity to introduce new functionality at the point of upgrade.



Benefits of Re-implementation

  • Faster to realise the value in the product: you’ll cleanse your data, improve processes and introduce new functionality so the business will begin to reap the benefits much faster after go-live.
  • Improved reporting: you’ll introduce a clean financial chart of accounts.
  • Cheaper in the long-term: consultant costs are higher ahead of go-live but you’ll gain the return on investment quicker.

Challenges of Re-implementation

  • Slower to go-live: a re-implementation takes around nine to 18 months.
  • There are more activities, such as migration of data, and you may need to export and rebuild some of your reporting and permissions.
  • More expensive in the short-term: consultant costs will be higher as the project will take longer.

More Knowledge

What is IFS Cloud?

The launch of IFS Cloud was a landmark for IFS. The new product is a step change from Apps 10. IFS Cloud is built on the latest technology stack and is 100% cloud-based.

What does evergreen in IFS really mean?

Evergreen requires a shift in mindset from thinking of ERP implementation as a single event, to adopting a cycle of continuous improvement.

Making the case for change

When you’re planning the move to IFS Cloud, you’re embarking on a programme to transform the whole business.