Importing Succession Data and Utilizing Calibration with Succession Planning

Importing Successors

Objective

After completing this lesson, you will be able to explain the components of the Successor Import Template and identify the actions available to import successors.

The Successor Import Template

The Import Successor feature allows you to add, update, delete, and transfer successors using a CSV file. The CSV file could contain successors from your external HRIS, or you can use Import Successors to maintain succession data after changing your nomination method.

Importing Successors is a three-step process:

  1. Download the Import Successors Template.
  2. Fill in the data that you wish to import, and the action the import will be performing.

    Based on the Action Type, enter the minimum required fields for a successful import.

  3. Import the Successors.

The import template is dynamically generated based on the succession nomination method being used in the application. This happens because you need different fields to update nomination data, depending on your nomination method. All template examples shown, unless noted differently, are for the MDF Nomination Method.

To download the successor import template:

  1. To navigate to Import Successors, use Action Search.
  2. Choose Export Template. The template can then be opened from the downloaded location.
Export Successor Import Template using the Export Template button.

There are four actions available using Import Successors:

  • ADD: Adds the successor nominee to a position
  • TRANSFER: Transfers the successor from one position to another
  • UPDATE: Updates the data for the successor nominee. For example, you can mass update/change readiness levels.
  • DELETE: Removes a nominee from a position

Note

  • Don't add a single user as the successor to hundreds of positions. This is to avoid display issues in, for example, the Current Nominations block in People Profile.
  • External successors cannot be imported.

Which fields will be filled out in the template depends on the ACTION you’ll be performing. The fields within the MDF nomination import template are as follows:

  • GENERIC_POSITION_CODE: Define the position code of the position that is being affected with the import. This field is required for all Position additions, updates, deletions, and transfers. It is not necessary for changes to Talent Pools.
  • OLD_GENERIC_POSITION_CODE: If a nominee is being transferred from one position to another, enter the OLD position code from which the nominee is transferring.
  • POOL_CODE: Define the Talent Pool code if editing nominees in a Talent Pool.
  • OLD_POOL_CODE: If a nominee is being transferred from one Talent Pool to another, enter the OLD Talent Pool code from which the nominee is transferring.
  • EMERGENCY_COVER: Designate a successor as an Emergency Cover. You can see it in the template if you've enabled the emergency cover feature in the Nominations Setup admin tool.
  • READINESS: Define the readiness level for the nominee being imported, using the Readiness Score number (from the Rating Scale) and not the label. This field is required for successor nominations, and for Talent Pool nominations if the Talent Pool is set up with readiness enabled.
  • SUCCESSOR_USERID: Define the ID of the successor. This field is required for the ADD or UPDATE actions. For TRANSFER or DELETE actions, if you leave this field empty, the action affects all existing successors and pending successors.
  • NOTE: Enter a note to be included in the nomination.
  • RANKING: Define the rank of the nominee. This field is optional. You can see it in the template if you've enabled successor ranking in the Nominations Setup admin tool.
  • ACTION: Define the ACTION that the import is performing.

Note

If you leave the action field empty or choose ADD or UPDATE, the behavior is the same. The system tries to update the existing record first. If no record is found, it creates a new one.

The MDF Template to Import Successors is displayed.

Once your data is entered into the template, you import the CSV file to make the changes to the succession plans. To import successors, follow these steps:

  1. To navigate to Import Successors, use Action Search.
  2. Select Choose File and browse to the location of your succession import template.
  3. Choose Import Successors.

Lesson Summary

The key learning points of this lesson are:

  • The Import Successor feature allows organizations to manage succession data (add, update, delete, transfer successors) in bulk using a CSV file. Successor nominations can be imported for positions or talent pools, with action types (ADD, UPDATE, DELETE, TRANSFER) determining the required fields. External successors cannot be imported, and single users should not be nominated for many positions to prevent system display issues.
  • ADD/UPDATE action requires `GENERIC_POSITION_CODE`, `SUCCESSOR_USERID`, `READINESS`, `EMERGENCY_COVER`, and `ACTION`.
  • DELETE action requires `GENERIC_POSITION_CODE`, `SUCCESSOR_USERID`, and `ACTION` (DELETE).
  • TRANSFER action requires `GENERIC_POSITION_CODE`, `OLD_GENERIC_POSITION_CODE`, `SUCCESSOR_USERID`, and `ACTION` (TRANSFER).
  • Custom fields like Talent Pool codes and rankings can be included based on template configuration.
  • In the Role-Person nomination method, successor nominations are tied to `UserID + Job Code`. When an employee’s Job Code changes, succession data tied to the old Job Code is lost. To retain nominations, use the Import Successors feature before the change to transfer nominations from the old to the new Job Code by editing fields (`JOBCODE`, `OLD_JOBCODE`, `INCUMBENT_USERID`, `OLD_INCUMBENT_USERID`, and `ACTION` set to TRANSFER). Email notifications provide import success and error details for troubleshooting.