Considerations for Migrating to V3 Seniority Dates

Here's some points to consider before you migrate to the new version (V3) from the earlier V1 or V2 version.

• Migrate from V1 to V3 while V2 exists

  • Select the Migrate Seniority Data from V1 version of Seniority process parameter.

  • After the migration, you can't view or modify V1 seniority dates.

  • You can no longer view or modify V2 seniority dates.

  • Create new rules for V3 seniority dates because all the V2 seniority date rules are inactivated.

• Migrate from V1 to V3 while V2 doesn't exist

  • Select the Migrate Seniority Data from V1 version of Seniority process parameter.

  • After the migration, you can't view or modify V1 seniority dates.

  • You can no longer view or modify V2 seniority dates.

• Migrate from V2 to V3 while V1 exists

  • Select the Migrate Seniority Data from V2 version of Seniority process parameter.

  • After the migration, you can't view or modify V2 seniority dates.

  • You can no longer view or modify V1 seniority dates.

  • Create new rules for V3 seniority dates because all the V1 seniority date rules are inactivated.

• Migrate from V2 to V3 while V1 doesn't exist

  • Select the Migrate Seniority Data from V2 version of Seniority process parameter.

  • After the migration, you can't view or modify V2 seniority dates.

  • You can no longer view or modify V1 seniority dates.

• No previous versions installed

  • New setup for V3 with no data migration.