Upgrade to v10 in the Cloud

We are currently on v9.0.0.9 and are considering transitioning from on-premise to the cloud when we upgrade to v10. I'd appreciate hearing from others who have transitioned their Lawson HR application from on-prem to the cloud--challenges you faced, time it took to transition, what do you think of the Mingle interfact, etc. Thank you!

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

unknown

I see this blog was posted nearly a year ago, but I will still share my experience to date. We are in the middle of our upgrade right now and it has not gone well from the beginning. A few disclosures before I begin. We are a small health care company; I was hired in May to manage the upgrade that initially started in January; we chose to work directly with Infor as our business partner for the upgrade; we are moving from an AIX 9.0.1 system to version 10 in the cloud.

With that said, here is the bad:
1) We use a Linux server that is not compatible with Active Directory. We have no way to authenticate into the cloud. This was missed during the scoping of our project. We are scrambling for a solution, and there are no cheap options.

2) Our Statement of Work spells out a couple conditions that I wish it had not (this is all on us). One would have hoped that any consulting firm would own these aspects:
A) We would handle our own customizations

We did not need any on premise consultants
C) We are responsible for our own test scripts,
D) There will not be a resource on Infor’s side from beginning to end.

3) It took 2 months to get a resource on the Infor side to do our data migration. Instead of starting in early May, we started in mid-July. Everything we request takes time because of the lack of resources.

4) The data migration was planned for 40 hours, it took closer to 80.

5) Our user setup process (manually done as a result of our authentication issues) took over a week and should have only taken 1 day. (This was setup in the wrong environment, and slow response).

6) There are a lot of additional applications that are a part of the Lawson product that we are responsible for installing. Ex: LID, IPA (new version of Process Flow), Excel Add-Ons. None of these were spelled out or scoped. We had to reach out to Infor to discover this.

7) We have spent over 3 hours discussing how we would prefer to be trained. Our small company cant afford to have our associates go down to on-site training for 5 days per topic (IPA, Landmark Differences and version 9 to 10 Differences). We still have not come to an agreement.

8) We are to begin testing prior to having our customizations or Mingle set up. These hopefully will be set for round 2 testing which is only supposed to be the remediation phase.

9) To try to stay on target for our timeline for testing was cut from 3 weeks to 1. (Not going to happen).

The Good:

1) Due to unforeseen circumstances our Infor PM was unable to continue to work on our project and we had to switch mid-stream. We had a really good replacement, plus our technical PM stayed in tack.

The reason I am posting this is because I looked long and hard for other people’s experience in blogs and did not see anything detailed that could have helped me avoid the situation we are in. I would like to stress half of these problems are self-inflicted, but by sharing my experience, hopefully others can learn and have a smoother transition.

unknown

We are going through a cloud migration as well and something important that came up for us recently, if you use Infor, is there are two types of data. Be careful to understand the implications and timing for the environmental data pull. We are backtracking because we did not fully understand that our LSF9 security was included in this pull and that we would have to manually track all provisioning after that data pull until go-live.

Environment Metadata (also call the Tech Migration)

This data is related to the setup and support of the system infrastructure, and is only migrated once in each environment with the source repository being v9 PROD. This type of migration includes data from the existing the Lawson LDAP, GEN/LOGAN database or file system. This is not a large data pool, however the process of extracting and loading is time consuming. Here are the list of things that will be taken;

- Users (only the ones in the LDAP)

- Security (non-laua)

- Services and Identities

- Job Definitions (taken in two formats, jobs and ujobs)

- Lawson Printer Definitions

- Job Queue Definitions

- Distribution Groups

- User Groups

- Bookmarks

- Calendars

- Locales

- Portal Roles

- User Info

- LOGAN LO and RD system codes

- Various file from the $LAWDIR/system folder

- ProcessFlows (the xml files)

- ProcessFlow metadata

Application Product Line (also call App Data)

This data is the setup and transactional data that has accumulated in the Application Product Line. This is the data associated to the work that was performed by the business units (outside of job definitions, which is part of the Environment metadata). Ideally, we would like to export this data from v9 PROD, however we can extract it from a Staging area too if Boyd’s want to move the data there instead.

unknown

Just another update on items to look out for with your migration. I would suggest that you make sure in your agreement that you include multiple data pulls. You will be able to validate the data in your new environment and see that a repeatable process has been developed to migrate your data. We might be in a unique situation since we are upgrading and migrating from a DB2 database to a SQL database.

Copyright © 2025 Infor. All rights reserved.