Preparing for your upgrade

Before your upgrade date, we strongly recommend taking time to review your existing data. Depending on your organization size and how long you’ve been a client, you may have extensive data in Legacy PI, and we want to make sure your upgrade experience is as seamless as possible.

By default, we’ll carry over the bulk of your data—including employees, candidates, jobs, teams, and surveys—to PI2. That said, a little bit of data hygiene ahead of time goes a long way. If your organization has hundreds or thousands of people records, doing some data preparation will ensure you can hit the ground running in PI2.

Here are some steps to help make for a smooth data transfer process:

Step 1: Verify that all current employees are tagged as “employees.”

In order to transfer your data correctly to PI2, it’s important that we know who in the system are current employees.

Even if someone in your organization has a PI data record, if that person isn’t properly tagged as an “employee,” we have no way of knowing they’re a current employee. As a result, you won’t see them in your employee directory in PI2.

How to solve: Follow the steps in this article and ensure all current employees are accurately tagged as “employees.”

Step 2: Verify that all active candidates are tagged as “candidates.”

Likewise, it’s important that any active candidates in your pipeline are tagged as a “candidate.” If you have incorrect tags, you may find that certain candidates don’t show up when you search for them in PI2.

How to solve: Follow the steps in this article and ensure all active candidates are accurately tagged as “candidates.”

Step 3: Ensure all current employees have a business email.

If an employee took the PI Behavioral Assessment back when they were a candidate, it’s possible their PI data is still tied to a “freemail” account, such as Gmail or Yahoo.

Once you’ve upgraded to PI2, we won’t know they belong in your employee directory unless you’ve done at least one of the following:

• You’ve tagged this employee as an “employee” (see Step 1).
• You’ve updated their email to their current business email.

How to solve: Either ensure you’ve followed Step 1 of this guide, or ensure that all current employees have an updated business email. To edit employee emails, refer to the “Edit and manage your users” section of this support article.

Step 4: Review employees with multiple BA results.

In the legacy experience, it was possible to resend and retake the PI Behavioral Assessment. Users could flip between multiple BA results, allowing them to see how an employee’s Self may have changed over time.

This functionality is not currently in PI2, but is coming in late Q2. Upon your upgrade date, we will carry over all employee BA results from legacy to PI2, including multiple BAs for a single person. However, until the ability to manage multiple BAs is live in late Q2, we will default employees with multiple BAs to their oldest set of BA results.

How to solve: In most cases, we expect this to be the most accurate BA data for a given employee. However, in the event you don’t want an employee’s BA to default to their oldest (e.g., someone with BA results older than six to eight years), there are two options to consider:

1. You can delete all but one set of BA results for an employee in legacy PI. Doing so will ensure the right BA results become their default in PI2. (Any legacy BA data you delete will be erased and thus won’t carry over to PI2.)
2. You can wait for late Q2, when PI2 adds the ability to manage multiple BA results. Once that functionality is live, you can select the employee’s “active assessment.” (Feel free to download resources in legacy PI before your upgrade date—such as the Placard or Behavioral Report—that the employee can use during the interim.)

Step 5: Upload an organization file (either in Legacy PI or in PI2).

At some point in your upgrade journey, we strongly recommend you take time to upload an org file. Even if you had pristine data hygiene in the legacy PI experience, uploading an updated file will help fill in any missing employee information.

Org upload is particularly important if you’d like to:

• Quickly send assessments to employees
• Grant software access in bulk to employees
• Set behavioral data permissions (requires an accurate list of current employees and their managers)

How to solve (pick one option):

• Upload an org file in your existing PI software: Follow the steps in this article before your upgrade date.
• Upload an org file in PI2: Follow the steps in this article after you’re upgraded to PI2.