ConfigBot DF - Pay Setup - Entitlement - Use Case 01 (Similar and Different ID's while Migration)

This article will help you understand the necessary steps and the impact of “ID” when moving entitlements from one instance to another.

1.     Enter your Username and Password and click at the submit button to login.

2.     Navigate towards the "Home screen" and click on the "Pay Setup" module tile under Platform.

3.     Select the workspace that best suits your preferences or requirements.

4. Lets Start by comparing the workbook from two different instances, to see the similarities and differences among them.

5. Once the compare is completed open the workbook to see the similar and different objects among both instances.

A. Here you can see the object named "2.0 EO - Initialize Work > 35" is not present in instance 02 and also there is no object with ID Number 14 in instance 02, which means we can simply migrate this object by setting the processing status to pending without changing the ID and once the object is migrated it will be created as new object without duplication and merging of rule sets.

B. In the second case, you can see that the object named ‘Sick - Hours - abc - Weekly - Award’ has ID number 04. Let’s say we want to migrate this object to Instance 02. In Instance 02, there is already an object named ‘Banked Dollars - Policy Assignment’ with the same ID.

If we proceed with the migration as-is, the similar ID will cause the object from Instance 01 to override the object in Instance 02, resulting in rule sets being merged and duplicated instead of creating a new object.

To prevent this, we must remove the ID from the object ‘Sick - Hours - abc - Weekly - Award’ before migration. This will allow the bot to create a new object in Instance 02 and generate a unique ID, avoiding any duplication or unintended merging of rule sets. Once the ID is removed you can set the processing status to pending

6. Once the objects are set to pending navigate back to your workspace and click at edit iteration button, now replace the instance 01 details to instance 02 as we are migrating the objects from instance 01 to instance 02.

7. Click at Hamburger Menu and select Start Configuration option, Enter your Dayforce Instance 02 object and add relevant notes, select entitlements check box and finally click at confirm and start button to process execution.

8. Once the processing status is completed open the workbook to confirm the migration, for the first case in which there was no similar ID you can see the object is successfully created with unique id without any duplication or merging of rule sets.

For second case in which we left the ID column blank to avoid duplication you can see that the new ID is automatically generated for this object and the migration is successful without any duplication or merging of rule sets.

9. Navigate to your Dayforce Instance 02 to validate the changes. Here, you can see that both objects have been successfully migrated without any copied or extra rule sets.

This concludes the successful migration process and outlines the necessary steps that need to be taken when migrating objects with similar and different IDs.

Updated on: 01/29/2026