Migrate HR data to scoped

HR data migration is a three-part process that requires verification, mapping, and migration.

  1. Verify that all the base data (tables) are correctly mapped to their scoped counterparts.
  2. If there are changed or custom HR tables in the non-scoped version that you want to migrate to scoped, update or add them for mapping.
  3. Migrate the data.

Verify mapping of base HR data

In the non-scoped version of HR, there are up to 26 base tables that are automatically mapped for migration to scoped. These tables have default columns and choice lists that are also automatically mapped for migration. By default, all base tables (and their corresponding columns and choice lists) should map automatically. You can verify that the mapping is correct.

Before you begin

Role required: sn_hr_migration.admin

Procedure

  1. Verify the base tables are correctly mapped to scoped.
    1. Navigate to HR Migration > Data Mapping > Table Mapping.
    2. In the Migration Tables list, verify that the base tables are correctly mapped to their scoped counterparts.
      Note: Some of the non-scoped tables are merged into a single scoped table.
      • If you have HR Core only:
        Table 1. Base and target tables for HR Core only
        Global HR table Scoped HR table
        hr_document_acknowledgement sn_hr_core_document_acknowledgement
        hr_document_template sn_hr_core_document_template
        hr_emergency_contact sn_hr_core_contact
        hr_link sn_hr_core_link
        hr_m2m_link_template_lookup sn_hr_core_m2m_link_template
        hr_position sn_hr_core_position
        hr_profile sn_hr_core_profile
      • If you have HR Core and HR Service Portal:
        Table 2. Base and target tables for HR Core and HR Service Portal
        Global HR table Scoped HR table
        hr_bank_account sn_hr_core_profile_bank_account
        hr_beneficiary sn_hr_core_beneficiary
        hr_benefit_provider sn_hr_core_benefit_provider
        hr_benefit_type sn_hr_core_benefit_type
        hr_dental_benefit sn_hr_core_health_benefit
        hr_direct_deposit sn_hr_core_direct_deposit
        hr_disability_benefit sn_hr_core_disability_benefit
        hr_document_acknowledgement sn_hr_core_document_acknowledgement
        hr_document_template sn_hr_core_document_template
        hr_emergency_contact sn_hr_core_contact
        hr_insurance_benefit sn_hr_core_insurance_benefit
        hr_link sn_hr_core_link
        hr_m2m_link_template_lookup sn_hr_core_m2m_link_template
        hr_medical_benefit sn_hr_core_health_benefit
        hr_op_report sn_hr_core_op_report
        hr_op_report_frequency sn_hr_core_op_report_frequency
        hr_op_report_type sn_hr_core_op_report_type
        hr_op_system sn_hr_core_op_system
        hr_op_system_to_report_type sn_hr_core_op_system_to_report_type
        hr_performance_issue_type sn_hr_core_disciplinary_issue_type
        hr_performance_warning_type sn_hr_core_disciplinary_warning_type
        hr_pharmacy_benefit sn_hr_core_health_benefit
        hr_position sn_hr_core_position
        hr_profile sn_hr_core_profile
        hr_retirement_benefit sn_hr_core_retirement_benefit
        hr_vision_benefit sn_hr_core_health_benefit
  2. Verify the base columns are correctly mapped to scoped.
    1. Navigate to HR Migration > Data Mapping > Column Mapping.
    2. Right-click the Migration table column and select Group By Migration table.
    3. For each table, click the arrow to expand the list of elements in that group. Verify that the base columns are correctly mapped to their scoped counterparts.
  3. Verify the base choice lists are correctly mapped to scoped.
    1. Navigate to HR Migration > Data Mapping > Choice List Mapping.
    2. Right-click the Global column name column and select Group By Global column name.
    3. For each column, click the arrow to expand the list of elements in that group. Verify that the choice lists are correctly mapped to their scoped counterparts.

What to do next

If you have changed or custom HR data that you want to migrate to scoped, map this data. Otherwise, you can begin migrating your HR data.

Map changed or custom HR data

If you changed any of the base tables or created custom HR tables that you want to migrate to scoped, you can update or manually add them for mapping. For changed or custom HR columns and choice lists, you can update or add them as well.

Before you begin

For custom tables, columns, and choice lists, create the target equivalent in the scoped version of HR. See Create a table.

Role required: sn_hr_migration.admin

Procedure

  1. Update or add your changed or custom HR tables.
    1. Navigate to HR Migration > Data Mapping > Table Mapping.
    2. Click New or open a record.
    3. Fill in the fields on the form.
      Table 3. Migration Table form
      Field Description
      Global table name Name of the global migration table.
      Active Check box to activate the global migration table. Only active tables are migrated when data migration runs.
      Scoped table name Name of the scoped target table.
      Order Order number for when data migration runs. Lower numbered tables are migrated before higher numbered tables.
    4. Click Submit or Update.
  2. Update or add your changed or custom HR columns.
    1. Navigate to HR Migration > Data Mapping > Column Mapping.
    2. Click New or open a record.
    3. Fill in the fields on the form.
      Table 4. Migration Column form
      Field Description
      Migration table Name of the global migration table.
      Global column name Name of the global column.
      Global column label Label of the global column.
      Global column data type Data type of the global column.
      Global column maximum length Maximum length of the global column.
      Advanced Select if a custom script will be used to perform the migration.
      Active Active status for the global column. Only active columns are migrated when data migration runs.
      Scoped column name Name of the scoped target column.
      Scoped column label Label of the scoped target column.
      Scoped column data type Data type of the scoped target column.
      Scoped column maximum length Maximum length of the scoped target column.
      Has Choice Select if the column has a choice list.
    4. Click Submit or Update.
  3. Update or add your changed or custom HR choice lists.
    1. Navigate to HR Migration > Data Mapping > Choice List Mapping.
    2. Click New or open a record.
    3. Fill in the fields on the form.
      Table 5. Migration Choice List form
      Field Description
      Migration column Name of the global migration column.
      Global choice name Name of the global choice list.
      Global choice value Value of the global choice list.
      Active Active status for the global migration choice list. Only active choice lists are migrated when data migration runs.
      Scoped choice name Name of the scoped target choice list.
      Scoped choice value. Value of the scoped choice list.
    4. Click Submit or Update.

What to do next

After you map all your changed or custom HR data, migrate it.

Migrate HR data

After you complete your data mapping, migrate your HR data from the non-scoped to the scoped version of HR.

Before you begin

Make sure that HR data mapping for your tables, columns, and choice lists is complete.

Role required: sn_hr_migration.admin

Procedure

  1. Navigate to HR Migration > Data Migration.
  2. Under Related Links, click Generate Pre Migration Report.
  3. After the Pre Migration report generates. Click Close.
  4. Under Run ID, click the report.
    The Migration Pre Run record displays. In the Migration Pre Results section, a list of changes to the tables, columns, and choice lists displays.
  5. Apply or skip the changes for migration.
    • To apply the changes for migration, select the check boxes for the applicable rows, and then select Apply as the action.
    • To skip the changes for migration, select the check boxes for the applicable rows, and then select Skip as the action.
  6. Click Apply Schema Changes.
  7. The Apply Schema Confirmation form displays. Click Confirm.
  8. After the schema update completes, click Close.
  9. Click Start Migration.
    A list of the HR tables to be migrated displays.
  10. Migrate the tables one at a time or in automatic succession.
    • To migrate the tables individually, click Migrate.
    • To automatically migrate the tables in succession, click Migrate All.

What to do next

If there is more changed or custom HR data that needs to be migrated, you can run the verification, mapping, and migration process again. Otherwise, HR data migration is complete.