You didn't mention any specs on what you have now (Unix vs windows, oracle vs sqlserver, etc....) In our case, we did on premise (we were Live on Infor 10 a/o May, 2015) We are AIX, oracle for LSF and Landmark. Full suite (fin/hr/payroll/smart office/POU/IPA) and the topic never came up to change platforms or go off site. I would think that would be a decision not taken lightly or just on a perceived cost savings. Under the timeline you now face, it may be difficult to fully flesh out all the pros and cons properly. As for the Infor claim that 'everybody is going to the cloud' I would only hazard a guess that this particular Infor person is not using the same 'facts' that are being presented to the rest of the user community. The last 'Infor 10-State of the Union' document I have seen was dated June-2015. At that time there were 120 customers live on Infor 10, of those, 85 were some type of upgrade of existing customers. It also had a Hosted vs. On-premise stat that I believe was representative of all 120 live Infor 10 customers and that was 65% On-premise and 35% hosted. So I can certainly see why they are unable to come up with 3 references.
If you want to see a document the could be considered "All things Infor 10" go to the inforxtreme support page and find KB # 1444526 or Topic # 29307 and you will find 10 pages of links to documentation for all things INfor 10. If you go to page 8, you will see a link to the State of the Union document mentioned above. The link is called "Lawson 10 SOTU presentation"
Good luck in your upgrade, May 2016 is starting to loom large on the horizon......
Jumping in late here but wanted to say DON'T believe Infor's hype on converting to Windows in the cloud. We are in the middle of a conversion and it is not going well because the cloud infrastructure and support are not ready for it. We've had nothing but problems from day one and continue to struggle with both Infor, Windows and V10.
We are upgrading and converting from Unix and V9.0.1 to Windows V10.0.5 for our entire Lawson suite - HR/PR, Finance, Supply Chain and Process Flow and adding several Landmark modules.
I completely agree with the previous reply that if you have a strong Lawson support team and System Admin...stay in-house.
We are in the process of converting from v9 on AMS hosted to v10 on AMS "cloud" hosted, and we've had several issues. One is that as AMS standardized how they treat hosted customers, they've placed additional restrictions on what they will let us do.
E.g., in our v9 hosted environment, they shared out the entire d:\lawprod\law folder, which, among other things, let us look at source, and config files when support would ask us to check something. Now, the won't share that, and it looks like we'll need to put in a lot more AMS service request incidents.
OTOH, they say they will give us more permissions on our "nonprod" (that's what they call "dev" now) servers, which is something they wouldn't do in the past. If that comes to pass, it will be very helpful.
Anyway, we're still early in the process, but we're happy to share what info we do have.
Just FYI, we did a 9.0.1 to 10 on-premise upgrade with Ciber and were very satisfied with the work they did. We did have them come on site, but my understanding is that most of their customers have them do all the work remotely. We have a small but savvy Lawson team and had the contractors come on site to educate our admins and also to help establish the new partner relationship.
We went through an RFP process to choose a partner, and I liked all of the 3rd party contractors we interviewed - Ciber, RPI, AVAAP, Absolute. All were priced very competitively and I would have been quite happy to go with any one of them.
In case of on premise upgrade - what is your strategy for Lawson Disaster recovery?
Did you install a separate DR instance for Lawson? If yes, how do you keep the DR instance in Sync with PROD in terms of CTP/MSPs, customization, security, etc.? Thank you.