Migrate Vendor Data to Acquisition Central

Award Management (AM) 2.6 and later includes a vendor data migration utility that transitions legacy AM vendor records to the unified Appian Acquisition Central data model. After migration, Acquisition Central serves as the single source of truth for vendor identity, eliminating duplicate data management across the Government Acquisition Management (GAM) suite.

This page describes the migration utility, its prerequisites, the 3-step migration process, and post-migration behavior.

What the vendor data migration utility does

The AM vendor data migration utility is a front-end administrative setup tool that moves legacy vendor data from the standalone AM vendor model to the centralized Acquisition Central vendor data model. The utility follows the same standardized 3-step framework established across other GAM solutions, such as Government Contract Writing (GCW), Government Source Selection (GSS), and Vendor Management (VM).

The Set Up Your Vendors dashboard walks administrators through the following sequence:

1. Review Vendor Data: Review your vendor records for completeness and correct any invalid data before reconciliation.
2. Reconcile Vendor Data: Match your vendors against Acquisition Central. Unmatched vendors are created automatically.
3. Migrate Vendor Data: Update award vendor references to use the shared Acquisition Central vendor record.

After the migration completes, AM users view and manage vendors through the Acquisition Central vendor record. The legacy AM vendor record is deprecated.

Prerequisites for vendor data migration

Before running the migration utility, ensure the following requirements are met:

• Acquisition Central: Version 26.6.1.6 or later must be installed and accessible in the environment. The unified vendor data model must be deployed.
• Award Management: AM 2.6 or later must be installed.
• User role: The user running the migration must have the Admin role in AM.
• Vendor identifiers: Legacy AM vendor records must have a valid Unique Entity ID (UEI) or CAGE code. These identifiers serve as primary keys in the Acquisition Central architecture.

Review vendor data

1. Go to Award Management Vendor Data Migration.
2. Click CONTINUE.

The Review step identifies vendor records with missing or invalid identifiers that must be corrected before reconciliation.

A banner at the top of the page shows the count of vendors with invalid data.

The Vendor List displays each vendor with its UEI, CAGE code, address, and status. Use the Status filter to narrow the list by any of the following statuses:

• Invalid Data: The vendor record is missing a required identifier, such as UEI or CAGE. Correct the record before reconciliation.
• Ready for Reconciliation: The vendor record has valid identifiers and is ready for the Reconcile step.
• Reconciliation Completed: The vendor record has been matched against Acquisition Central during the Reconcile step.
• Migration Completed: The vendor record has been migrated to Acquisition Central and its award references have been updated.

To review vendor data:

1. Use the Search Vendor field or the Status filter to locate vendor records.
2. For a vendor with a status of Invalid Data, click the action menu and select Update Vendor.
3. On the Update Vendor form, complete the required fields marked with an asterisk, such as Vendor Name, UEI, Address Line 1, City, State, and Zip Code.
4. Click SAVE.
5. Repeat for each vendor with invalid data until all records show a status of Ready for Reconciliation.
6. Click START DATA RECONCILIATION.

Reconcile vendor data

The Reconcile step compares vendor data from Award Management and Acquisition Central and imports missing vendors. The utility matches AM vendor records against Acquisition Central using the UEI and CAGE combination:

• No match in Acquisition Central: The utility creates a new vendor record in Acquisition Central.
• Match in Acquisition Central: The utility links the AM award references to the existing Acquisition Central record.

Both the UEI and CAGE values must match exactly for a positive match, including null values. A null CAGE is treated as a distinct value representing the corporate entity generically.

After starting reconciliation, the utility displays a Reconciling Vendor Data status while it compares vendor data and imports missing vendors.

To reconcile vendor data:

1. Wait for reconciliation to complete.
2. Click START DATA MIGRATION.

Migrate vendor data

The Migrate step updates award vendor references to use the shared Acquisition Central vendor record. After this step completes, awards reference vendor records in the Acquisition Central data model, and the legacy AM vendor record is deprecated.

When the migration finishes, the utility displays a Migration Completed confirmation showing the number of vendors migrated to Acquisition Central and confirming that all award vendor references have been updated.

To complete the migration:

1. After starting the migration, wait for the utility to update the award vendor references.
2. Review the Migration Completed confirmation, which shows the number of vendors migrated and confirms that all award vendor references have been updated.
3. Click BACK TO DATA VIEW to return to the vendor data view.

Post-migration vendor management

After the migration completes, all vendor management in AM is handled through Acquisition Central. The following changes take effect:

• Vendor viewing: AM users view vendors through the Acquisition Central Vendor Directory. The legacy AM Vendors page redirects to Acquisition Central.
• Vendor creation: AM users with appropriate permissions create vendors in Acquisition Central, either manually or by importing from SAM.gov.
• Vendor updates: Acquisition Central vendor data is synced with SAM.gov. SAM.gov is the authoritative source for vendor identity data such as registration details, certifications, and proceeding data.
• Award-specific data: The per-award transactional vendor record in AM continues to store award-specific vendor data, such as the vendor point of contact (POC). USASpending.gov sync updates this record directly.
• Vendor Summary Report: After migration, AM users access the Vendor Summary Report powered by ProcureSight Enterprise (PSE) from the Acquisition Central vendor record. The report compiles registration details, certifications, and proceeding data from SAM.gov. Contracting Officers, Contract Specialists, and Contracting Managers generate and regenerate reports, while Program Managers, CORs, and IT/Policy/Legal users view and download existing reports. The Vendor Summary Report is a federal-only feature and is not available to State and Local Government (SLG) customers.

For details on how the USASpending sync interacts with Acquisition Central after migration, see Vendor data handling after vendor migration.

Field mapping and data constraints

During migration, the utility maps legacy AM vendor fields to the Acquisition Central vendor data model. The following constraints apply:

AM field	Acquisition Central field	Constraint
Address Line 1	Address Line 1	Truncated to 150 characters from 255.
Address Line 2	Address Line 2	Truncated to 150 characters from 255.
Zip Code	Zip Code	Truncated to 5 characters from 20.
Zip Code Ext	Zip Code Extension	Truncated to 4 characters from 20.
POC	N/A	Retained on the per-award vendor record. Not migrated to Acquisition Central.
UEI	UEI	Migrated as-is. Required field.
CAGE	CAGE	Migrated as-is.

Vendor data handling during reconciliation

When reconciling AM vendor data against Acquisition Central, the utility follows these rules:

• Acquisition Central field is populated, AM field has a different value: The Acquisition Central value is retained. SAM.gov is the authoritative source for vendor data in Acquisition Central.
• Acquisition Central field is null, AM field is populated: The AM value is copied to Acquisition Central, supplementing missing data.
• Both fields are null: No action is taken for that field.

Limitations

The following limitations apply to the vendor data migration utility:

• No custom field migration: The migration utility assumes the standard AM vendor schema. Custom fields added by customers are not migrated automatically.
• No bidirectional sync: After migration, Acquisition Central is the sole source of truth for vendor data. Changes in Acquisition Central do not flow back to the deprecated AM vendor record.
• UEI or CAGE required: Vendor records without a valid UEI or CAGE code are not eligible for automated migration. Correct these records during the Review step before proceeding.
• No bulk report generation: Vendor summary reports are generated one vendor at a time through Acquisition Central.

Related pages

• USASpending Integration: Describes how the USASpending sync handles vendor data after migration.
• Set Up UAM: Configure user access for vendor-related permission sets.
• Roles and Permissions: View which roles have access to vendor management actions.

Feedback