> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/engage/partners/migrate-from-legacy/import-the-workbook.md).

# Import the Workbook

Upload the reviewed migration workbook through the Partner Importer and resolve any errors.

The final step creates the records. Until you run it, nothing in PEARS has changed.

## Where to Find It

{% stepper %}
{% step %}

#### Open the Partner Importer

Click the **cog icon** in the top navigation bar and select **Partner Importer**. The entry appears only when the Partners module is turned on for your organization and you have permission to run a migration. See [Requirements](/engage/partners/migrate-from-legacy.md#requirements).

{% hint style="info" %}
**TIP:** There is no template to download from that page. The workbook comes from the [Export to Partners](/engage/partners/migrate-from-legacy/export-to-partners.md) action, and the page links back to the two legacy lists to say so.
{% endhint %}
{% endstep %}

{% step %}

#### Upload the workbook and start the import

The import runs in the background with a progress indicator.
{% endstep %}
{% endstepper %}

## The Import Is All-or-Nothing

Every sheet is processed inside a single transaction. If any row on any sheet fails validation, the entire import is rolled back — you will not end up with half a migration.

When that happens, PEARS hands back a copy of your workbook named `<your file> - with errors.xlsx`. It contains:

* An **Errors** sheet at the end, listing every problem as sheet, cell reference, and message. Each cell reference is a hyperlink that jumps straight to the offending cell.
* The original sheets, with the failing cells highlighted in red.

Fix the problems in the error file and upload **that** file. Re-running clears the old highlighting, so you can iterate on the same document until it goes through cleanly.

{% hint style="warning" %}
**NOTE:** The importer never matches against existing records. Every import creates new Partners, so importing the same workbook twice produces two complete sets. Import each workbook once, and confirm the result before running another.
{% endhint %}

## After a Successful Import

* **Spot-check a few Partners you know well** — one with a long history, one that was split across units, one with attachments.
* **Confirm the report count** on a Partner matches the number of legacy records it came from.
* **Remember that nothing in Partnerships or Coalitions was changed.** The legacy records are still there, still reportable, and still attached to their original files.

{% hint style="info" %}
**TIP:** After a successful import, each new Partner's **External ID** field is set to the `partner_id` it had in the workbook, so you can tie a Partner back to the row that created it.
{% endhint %}

## Related Documentation

* [Mapping Reference](/engage/partners/migrate-from-legacy/mapping-reference.md) — What each legacy field became.
* [View Partner Details](/engage/partners/partner-details.md) — The roll-ups on a finished Partner record.