Perform an Org Unit Migration

  • Updated

Use Org Unit Migration when Org Units have been removed and replaced with new records. And you need to reconnect existing transaction data to the new Org Units. This feature updates Purchase Orders, Requisitions, and other transactions that currently contain Org Unit values as text. Ultimately, re-mapping historical transaction data to active Org Units.

 

When to Use This Feature

  • Accidentally removed all existing Org Units or
  • Uploaded all new Org Units

That left historical Purchase Orders and Requisitions disconnected from their Org Units. When this occurs, the Org Unit value remains as plain text (un-linked); rather than a linked Org Unit record.

Org Unit Migration allows Administrators, to restore these links without requiring manual database corrections.

 

Example of a Linked Org Unit:

 

Example of an Un-Linked Org Unit:

 

Prerequisites

Before running an Org Unit Migration:

  • User must have the Community Administrator role. 
  • The replacement Org Units must already exist, in Unimarket.
  • You must prepare a migration file containing legacy and active Org Unit mappings.
  • The Org Unit codes in the file must exactly match the values stored, in Unimarket.

 

Limits and Notes

  • Org Unit Migration updates existing transaction data only.
  • This feature is designed to eliminate the need for manual transaction corrections after Org Unit replacement activities.

 

Permissions

  • Users with the Community Administrator role, can manage these structures.

 

Access Managing Organizations Screen

  1. Navigate to the Administration module.

  2. Select Organizations.

  3. Click More Actions.

  4. Select Migrate Org Units.

 

Prepare the Migration File

  1. Select Download Template, to retrieve the mandatory CSV file template 
  2. Insert the applicable information in the required fields.
    • Legacy Org Unit Code = The Org Unit code currently stored as text on historical transactions.
    • Active Org Unit Code = The active Org Unit code that transactions should be linked to.
  3. Insert applicable unlinked Org Unit number(s) and name(s), in the template file.
  4. Once completed, save file in .csv format.

 

Example

Column A (Legacy Org Unit Code) Column B (Active Org Unit Code)
PVC000 CAREER SERVICES
PVC000 CAREER SERVICES

 

Import (Upload) the Migration File

Unimarket will search for transactions containing the value specified in Legacy Org Unit Code column. And re-map the transaction to the Org Unit identified in Active Org Unit Code column.

  1. Select Browse and click the migration file.
  2. Once completed, select OK.
  3. Review the uploaded data and confirm the mappings are correct.
  4. Review the processing results in File Processing (on the left side panel).

 

View Migration Results

For each row in the uploaded file, the system displays:

  • Processing status
  • Success or failure messages
  • Number of transactions updated
  • Any validation or matching errors

 

Results

After the migration completes:

  • Transactions containing the legacy Org Unit values are updated.
  • Purchase Orders and Requisitions are re-linked to active Org Units.
  • Org Unit data is restored as a system relationship rather than remaining as plain text.
  • Migration results are recorded in File Processing.