Preparing Lattice for an HRIS Vendor Switch

When switching HRIS vendors, it is important to reach out to your Relationship Manager or Customer Care to ensure your Lattice experience is not interrupted during the migration.

1. Disconnect all HRIS Custom Fields in Lattice.

To ensure that your HRIS custom fields map back into Lattice when switching providers, you must disconnect your fields before disconnecting the original integration. This process will not delete the field or the values for each employee.

Your original HRIS provider may be using different identifier External IDs than your current system. Therefore, you need to remove the old IDs from our system to ensure employees continue to be updated after the switch. 

When disconnecting, you will also have the option to remove external IDs. This would remove the external IDs tied to each user. If you were to integrate again, IDs would be reassigned using the emails as the unique identifier between the two systems.  

You can learn how to perform the disconnection process in Disconnect your HRIS integration from Lattice.

Import Log shows "External IDs do not Match" error.
When switching HRIS systems in Lattice, you may come across the error message "External IDs do not Match," preventing your employees from being updated. This error signifies that your previous system's External ID does not match with the External ID your current system is using. The result is that the integration no longer maps to Lattice.

In this case, you will need to reach out to your Relationship Manager or Customer Care to resolve the issue.

HRIS-synced Custom Fields not Updating
If you find that your previously synced Custom Fields are no longer updating, please reach out to your Relationship Manager or Customer Care to resolve the issue.