Gender Data Migration Overview

Enhanced Employee Gender Playbook
Version
R2025.1.0
Gender Data Migration Overview

The Gender Data Migration is a core feature of Enhanced Employee Gender. The Gender Data Migration feature moves customers from the Dayforce legacy schema to the enhanced schema. This process is required because our existing ways of holding gender and gender identity in Dayforce are incompatible with the new features that Enhanced Employee Gender supports. The Gender Data Migration uses a database script during the update from Dayforce Release 2024.2.1 to Dayforce Release 2025.1.0. Customers don’t need to take any actions during the migration process.

Customer Data and Migration to Enhanced Employee Gender

Two sets of data are involved in the migration from the current schema to Enhanced Employee Gender.

 

Schema migration datasets
Dataset What Dayforce does with the dataset during migration

Employee gender and gender identity information.

Note: This dataset doesn’t include non-employees like emergency contacts, dependents and beneficiaries, and others. Their gender and gender identity information isn’t affected by the new Enhanced Employee Gender functionality.

After the migration, employees will have the following as part of their gender record:

  • Country
  • State/Province
  • Assigned Sex
  • Gender Identity
Existing gender identity system configuration from HR Admin > Gender Identity.

Any existing gender identity configuration that was previously mapped to a country is automatically mapped to the same country in the new gender administration screen (HR Admin > Employee Gender Admin > Gender).

Any existing gender identity configuration that wasn’t previously mapped to a country, or that was mapped to several countries, is moved into Migrated Gender Identity Configuration. Customers can do one of the following things with this information:

  • Move this information into a country and make it country-specific.
  • Leave this information in this location, so that it’s available to all employees.

Migration Examples - Employee Gender Data

Employee 001 example of gender data migration
Pre-migration Notes
Pay group country Gender Gender Identity State/Province isn’t provided automatically because it can’t be reliably determined. After the employee interacts with their record, they’re asked to provide their state or province.

United States

 Male -----
Post-migration
Pay group country State/Province Assigned Sex Gender Identity
United States ---- Male ----
Employee 002 example of gender data migration
Pre-migration Notes
Pay group country Gender Gender Identity State/Province isn’t provided automatically because it can’t be reliably determined. After the employee interacts with their record, they’re asked to provide their state or province.

Canada

 Female Female
Post-migration
Pay group country State/Province Assigned Sex Gender Identity
Canada ---- Female Female
Employee 003 example of gender data migration
Pre-migration Notes
Pay group country Gender Gender Identity N/A

United Kingdom

 Male Non-Binary
Post-migration
Pay group country State/Province Assigned Sex Gender Identity
United Kingdom ---- Male Non-Binary
Employee 004 example of gender data migration
Pre-migration Notes
Pay group country Gender Gender Identity Gender identity isn’t supported legally in Germany, and will be removed.

Germany

 Indeterminate Indeterminate
Post-migration
Pay group country State/Province Assigned Sex Gender Identity
Germany ---- Indeterminate ----
Employee 005 example of gender data migration
Pre-migration Notes
Pay group country Gender Gender Identity NULL values weren’t possible before Enhanced Employee Gender, but the record is migrated as such.

France

 ---- ----
Post-migration
Pay group country State/Province Assigned Sex Gender Identity
France ---- ---- ----

Migration Examples - Gender Identity Configuration

Example 1: Gender identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country No country previously configured against this gender identity, moved to Migrated Gender Identity Configuration because all records must now be bound against a country.

Non-Binary

 NB_001 ----
Post-migration
Gender Identity Name Gender Identity Reference Code Country
Non-Binary NB_001 Migrated Gender Identity Configuration
Example 2: Gender identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country This “MALE” isn’t the system MALE record, but a custom one. This record will be removed as a duplicate and employees will be moved to the system MALE gender identity.

MALE

 MALE ----
Post-migration
Gender Identity Name Gender Identity Reference Code Country
---- ---- ----
Example 3: Gender identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country Migrated successfully into Belgium.

Indeterminate

 ID_BL Belgium
Post-migration
Gender Identity Name Gender Identity Reference Code Country
Indeterminate ID_BL Belgium
Example 4: Gender Identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country Removed from the system because Germany doesn’t allow for the legal collection of gender identity data.

Non-Binary

 NB_DEU Germany
Post-migration
Gender Identity Name Gender Identity Reference Code Country
---- ---- ----
Example 5: Gender identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country Moved to Migrated Gender Identity Configuration because the gender identity is tied to more than one country.

Male

 Male_UKFR United Kingdom, France
Post-migration
Gender Identity Name Gender Identity Reference Code Country
Male Male_UKFR Migrated Gender Identity Configuration
Example 6: Gender identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country

Moved to Migrated Gender Identity Configuration because configuration for the United States now occurs at the state level. Customers can move these records into their respective states or leave them under Migrated Gender Identity Configuration.

Non-Binary

 Non-Binary_US United States
Post-migration
Gender Identity Name Gender Identity Reference Code Country
Non-Binary Non-Binary_US Migrated Gender Identity Configuration
Example 7: Gender identity data migration
Pre-migration Migration Result
Gender Identity Name Gender Identity Reference Code Country Moved to Migrated Gender Identity Configuration because configuration for Canada now occurs at the provincial level. Customers can move these records into their respective provinces or leave them under Migrated Gender Identity Configuration.
Not Specified NS_CA Canada
Post-migration
Gender Identity Name Gender Identity Reference Code Country
Not Specified NS_CA Migrated Gender Identity Configuration

Enhanced Employee Gender Migration Log

To inform you of the changes made to your system data, Dayforce generates a migration log the first time that you access HR Admin > Employee Gender Admin > Gender. See Enhanced Employee Gender Migration Log.