Hello
Can any IFS Customers, Partners or IFS Consultants in the Community elaborate on an upgrade you’ve made from IFS App9 to the Cloud?
We are in App9 UPD14, we are debating to go through App10 or not. What do you think?
We have quite a lot of customizations and configurations and maybe, only maybe, some of them will not be needed after the upgrade.
Thanks!
Hi
Hi
How is the progress with your upgrade to cloud?
We have just started looking at the academy for training and received our first install to start testing with. We have not even got that up and going yet. No real experience with the APP other than sandbox/race environment.
Basically, nothing to report yet.
We are going through the same upgrade consideration process as the original poster Apps9 v17.
We initially were going via Apps10 route, but worked out very expensive with restricted support looming for apps 10.
We are now scoping for the on-prem version of IFS Cloud, with an aggressive timeline of 9 months. The board are looking for us to provide an overview of the business benefit due to the sheer cost and struggling to justify beyond being on a supported release (I don’t like the idea of the business falling so far behind with versions, I know the application will get developed to a point it will get even harder to move!), limiting risk with security patches and mobile functionality!
Added to the problem that we would like to get costing for the asset management module in 9 and IFS have not been able to quote with them pushing cloud so hard it’s very difficult to justify the cost and effort!
Does anyone know from IFS existing 5.5k customer list how many are actually on legacy/ support restricted versions??
We INNEX have a customer live coming from APPS9 to Cloud since 2 month.
In case you want to collaborate, feel free to reach out.
Coming up on 2 years since we made the initial inquiry to IFS on the upgrade….still not live, still working through it. The newer versions are getting close to what is required, but it has been an arduous road.
Just re-read this thread. We have recently started the upgrade from 9 to 10 project that I mentioned above and the golive date in prod is almost a year from now. We have a bunch of customizations (n ~200).
Our biggest reasons not to jump to IFS Cloud directly:
A) upgrading the customizations without having to re-plan every process at once (which would have required waay too much effort. It would be a partial re-implementation with changes needed to many e2e processes and also to other connecting systems).
B) continue using IEE to avoid a big bang project
C) agreement related reasons
We have tried to “cut the elephant to smaller pieces” by doing a technical code upgrade first and acknowledge that there are many continuation projects to do when first in IFS10. These include the integration technique change to using rest api’s, the switch to Aurena UI and some internal component switchovers from older to newer component (like budgeting functionalities).
At the same time it already worries a lot thinking about the possible later Cloud project. How can you have a reasonable business case to justify the project financially? How can you get rid of your customizations if the result is that effectiveness suffers and manual work increases. It sounds like reinventing the wheel when you have to re-implement all your processes (A on the list above) moving from 10 to Cloud.
Just an update on my previous comments on this discussion. We have now been live in IFS10upd16 for a month and situation is fairly stabile. The project went on schedule but a lot over budget thanks to f.ex. higher than anticipated work related to keepin the customizations along. We did get rid of some CRIM’s, mostly in areas like HR where we have moved to other solutions. Most of the other CRIM’s we still need because getting rid of them would cause more manual work or getting rid of them would cost more than continue paying for them until the Cloud project starts.
Now the focus is shifting to the above mentioned “continuation projects” where the aim is to pave way for the Cloud version.
One of my main concerns regarding Cloud right now is to have a realistic understanding of the money and resources needed to keep along in the Release-and-update train. There are some good videos here on Community explaining this that I have to look deeper into but in general I’d appreciate less marketing talk and more hard facts about the requirements the Cloud version has to a customer compared to the older Apps versions.
We have bitten the bullet and signed the contract to upgrade from IFS APPS9 to Cloud! Anyone else on the same journey? Am curious on how easy it is to uplift your crims?
Coming up on 2 years since we made the initial inquiry to IFS on the upgrade….still not live, still working through it. The newer versions are getting close to what is required, but it has been an arduous road.
Can I ask Shawn what your biggest pain points are? I was hoping that the later releases would have eased some of the bug issues.
Are you getting reasonable support now from IFS?
As a customer coming from a different ERP to the IFS Cloud 22R2.
At this point having a similar implementation timeline as
Our biggest painpoints are:
At this point (22R2) I would not recommend anyone moving to IFS Cloud.
Can I ask Shawn what your biggest pain points are? I was hoping that the later releases would have eased some of the bug issues.
Are you getting reasonable support now from IFS?
Sorry to make you wait for a reply, but I have to be a bit more reserved about my criticisms on here as it ruffles too many feathers….I’ll try to keep it general.
Pain Points:
The project was put on hold for 2023 essentially and is only now being revisited, that should tell you in a nutshell how the interaction has been from a product maturity and support standpoint.
Be prepared to do it all on your own or don’t plan on doing it.
My apologies for leaving you both hanging, I had nothing to offer at the time and didn’t get back to either of your direct questions. Hope your experience has been anything better than mine.
No worries
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.