How does Legacy Data get onto the Cloud?

We’ve discussed a lot about implementing GHR Multi-Tenant Payroll on this blog, so let’s dive into some of the specifics of the system. Payroll History Import is a business class delivered by Infor that allows you to bring S3 data over to GHR. This means you still have access to historical data and the ability to review payroll, the pay employee paychecks, and other kinds of details in GHR, instead of having to access S3 data. As we have said many times before, you should limit what you bring over to that GHR system. We recommend no more than one year of data, unless it is detrimental to your current business processes. Later on, we will discuss the ramifications of bringing over more than a year – it is feasible and we have done it before, but you want to consider what’s absolutely necessary as far as historical data.

Of course, this payroll is the re-import and it contains three main records: employee payments, wages, and deductions. This may seem like quite a lot of stuff to go through to load all that data, but it comes down to a handful of steps that you should pay attention to throughout the conversion process. The core of this is the RPI interface, which is the whole aspect of Payroll History Import. We built an interface to extract that data from all the main S3 tables related to payroll governed by parameters to control what you're trying to extract out of the legacy system. 

In a nutshell, you import your historical data, the system runs the conversion process, and then you can manually fix any errors that may have come up. When you are correcting these, we recommend using an ISD download and upload if you want to change anything, unless you miss a pay code name. In that situation, you want to rename it instead of purging everything again and starting over. Afterwards, you can do a massive upload and reprocess that data to make sure everything is correct.

Of course, we monitor all these steps I mentioned here like the database import and anything that uses an async process (although you should be doing this as well). This should be done not just on the screen where you’re monitoring the non-process and error tab, this, but you also want to monitor those async processes to make sure they don't fail. When an async fails, your process will just sit there and nothing will happen, even though you may think it’s running. Having both our team and yours keep an eye on this prevents any holdup when you go to run your payroll at the end of a pay period.

Once you've done one month, you go through it and keep loading the next month until you have finished. I recommend you load all your data through the import and run this process because that creates all pending payments, which is something you need to do for each of those months. For example, if you have eight months to upload for 2021, you want to do this process all the way through. That's just a brief overview of what the overall end-to-end process is and how it runs.

Learn More about RPI Consultants

Back to Blog

Related Articles

Payroll Admin Dashboard, Lock Payroll, & More: New Features in CloudSuite

We’re going to discuss some of the newest payroll features on CloudSuite. The first one I would...

How does Lock Payroll work?

Last week, we covered some of the new and exciting features of GHR Multi-Tenant Payroll like the...

The Integration of Payroll & Finance in GHR

The last element of GHR Multi-Tenant Payroll that I want to cover is the integration between...