Amazon Seller Partner Migration Guide

Availability

Core Standard Plus Pro Enterprise Flex PyAirbyte

Support Level

Airbyte

Connector Version

5.10.2 (last updated 18 days ago)

Sync Success Rate

High

Usage Rate

High

Data workers used

0.2 per sync (Learn more)

Definition ID

e55879a8-0ef8-4557-abcf-ab34c53ec460

Upgrading to 6.0.0

The primary key has been removed from the GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL and GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL streams.

These Amazon flat-file reports contain one row per order item, so the previous primary key (amazon-order-id) is not unique: when these streams were synced with Incremental | Append + Deduped, the destination collapsed all line items of a multi-item order into a single row, silently dropping data. No column or combination of columns in these reports has been proven to be reliably unique per row, so the streams now have no primary key.

After upgrading, refresh the source schema for your connection. Then:

If either stream used Incremental | Append + Deduped, your destination table is missing line items and must be reloaded:

danger

Clearing a stream deletes its data in the destination. Amazon only supplies order reports for orders less than two years old, and the connector only requests data from your Replication Start Date onward, so rows older than that cannot be re-synced. Take a snapshot or backup of the two destination tables before clearing if you need that history.

1. Change the sync mode of GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL and GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL to Incremental | Append (or Full Refresh | Overwrite). Incremental | Append + Deduped is no longer offered for these streams.
2. Clear both streams and run a sync.

If these streams used Incremental | Append, Full Refresh | Append, or Full Refresh | Overwrite, no further action is required. Your existing rows are complete; do not clear the streams.

Downstream impact. After the reload, these tables contain one row per order item, not one row per order. Update SQL, dbt models, and dashboards that count rows as orders or that assume amazon-order-id is unique (for example, use COUNT(DISTINCT "amazon-order-id") for order counts, and group by amazon-order-id before summing item-level amounts). If you use a lookback window, deduplicate downstream on the full row or on _airbyte_extracted_at, since the destination no longer deduplicates for you.

Upgrading to 5.0.0

Two deprecated FBA Subscribe and Save report types have been removed from the connector per Amazon SP-API deprecation:

• GET_FBA_SNS_FORECAST_DATA (Subscribe and Save Forecast Report)
• GET_FBA_SNS_PERFORMANCE_DATA (Subscribe and Save Performance Report)

These report types were deprecated by Amazon and will return empty responses starting July 25, 2025, and will be completely removed on December 11, 2025. See Amazon's deprecation notice for more details.

Action Required

If you have these streams enabled in your connection:

1. Refresh the source schema to remove the deprecated streams from your catalog
2. No data reset is required - these streams are simply being removed from the available streams list

Steps to Update

1. Select Connections in the main navbar.
   1. Select the connection(s) affected by the update.
2. Select the Replication tab.
   1. Select Refresh source schema.
   2. Select OK.

The deprecated streams will no longer appear in your available streams list.

3. Select Save changes at the bottom of the page.

No data reset is required for this upgrade as the streams are being removed, not modified.

4. Select Save connection.

For more information on managing your Airbyte connections, see the Airbyte documentation.

Upgrading to 4.0.0

Stream GET_FBA_STORAGE_FEE_CHARGES_DATA now has updated schema, which matches Amazon Seller Partner docs.

Users will need to refresh the source schema and reset this stream after upgrading.

Refresh affected schemas and reset data

1. Select Connections in the main navbar.
   1. Select the connection(s) affected by the update.
2. Select the Replication tab.
   1. Select Refresh source schema.
   2. Select OK.

Any detected schema changes will be listed for your review.

3. Select Save changes at the bottom of the page.
   1. Ensure the Reset affected streams option is checked.

Depending on destination type you may not be prompted to reset your data.

4. Select Save connection.

This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page.

Upgrading to 3.0.0

Streams GET_FLAT_FILE_ALL_ORDERS_DATA_BY_ORDER_DATE_GENERAL and GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL now have updated schemas.

The following streams now have date-time formatted fields:

Stream	Affected fields	Format change
GET_AMAZON_FULFILLED_SHIPMENTS_DATA_GENERAL	estimated-arrival-date	string YYYY-MM-DDTHH:mm:ssZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_LEDGER_DETAIL_VIEW_DATA	Date and Time	string YYYY-MM-DDTHH:mm:ssZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_MERCHANTS_LISTINGS_FYP_REPORT	Status Change Date	string MMM D[,] YYYY -> date-time YYYY-MM-DD
GET_STRANDED_INVENTORY_UI_DATA	Date-to-take-auto-removal	string YYYY-MM-DDTHH:mm:ssZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE	settlement-start-date, settlement-end-date, deposit-date, posted-date	string YYYY-MM-DDTHH:mm:ssZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_MERCHANT_LISTINGS_ALL_DATA	open-date	string YYYY-MM-DD HH:mm:ss ZZZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_MERCHANT_LISTINGS_DATA	open-date	string YYYY-MM-DD HH:mm:ss ZZZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_MERCHANT_LISTINGS_INACTIVE_DATA	open-date	string YYYY-MM-DD HH:mm:ss ZZZ -> date-time YYYY-MM-DDTHH:mm:ssZ
GET_MERCHANT_LISTINGS_DATA_BACK_COMPAT	open-date	string YYYY-MM-DD HH:mm:ss ZZZ -> date-time YYYY-MM-DDTHH:mm:ssZ

Users will need to refresh the source schemas and reset these streams after upgrading.

Refresh affected schemas and reset data

1. Select Connections in the main navbar.
   1. Select the connection(s) affected by the update.
2. Select the Replication tab.
   1. Select Refresh source schema.
   2. Select OK.

Any detected schema changes will be listed for your review.

3. Select Save changes at the bottom of the page.
   1. Ensure the Reset affected streams option is checked.

Depending on destination type you may not be prompted to reset your data.

4. Select Save connection.

This will reset the data in your destination and initiate a fresh sync.

For more information on resetting your data in Airbyte, see this page.

Upgrading to 2.0.0

This change removes Brand Analytics and permanently removes deprecated FBA reports (from Airbyte Cloud). Customers who have those streams must refresh their schema OR disable the following streams:

• GET_BRAND_ANALYTICS_MARKET_BASKET_REPORT
• GET_BRAND_ANALYTICS_SEARCH_TERMS_REPORT
• GET_BRAND_ANALYTICS_REPEAT_PURCHASE_REPORT
• GET_BRAND_ANALYTICS_ALTERNATE_PURCHASE_REPORT
• GET_BRAND_ANALYTICS_ITEM_COMPARISON_REPORT
• GET_SALES_AND_TRAFFIC_REPORT
• GET_VENDOR_SALES_REPORT
• GET_VENDOR_INVENTORY_REPORT

Customers, who have the following streams, will have to disable them:

• GET_FBA_FULFILLMENT_INVENTORY_ADJUSTMENTS_DATA
• GET_FBA_FULFILLMENT_CURRENT_INVENTORY_DATA
• GET_FBA_FULFILLMENT_INVENTORY_RECEIPTS_DATA
• GET_FBA_FULFILLMENT_INVENTORY_SUMMARY_DATA
• GET_FBA_FULFILLMENT_MONTHLY_INVENTORY_DATA

Connector upgrade guide

Review the following information to prepare for and execute your upgrade.

Review the changelog

Before updating a connector, review the changelog to understand the changes and their potential impact on your existing connections. Find the changelog for any connector by navigating to the bottom of the documentation for that connector. Major version releases also include a migration guide.

Plan for major updates

Major updates may require you to adjust connection settings or even make changes to your data pipelines. Allocate enough time and resources for this. Use the migration guide to ensure your transition process goes smoothly.

Airbyte provides tooling that guarantees safe connector version bumps and enforces automated version bumps for minor and patch updates. You always need to manually update for major version bumps.

Self-managed plans: pin a specific version if you can't update

If you're unable to upgrade to the new version of a connector, you can pin that connector to a specific version.

1. In the navigation bar:

   • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

   • If you're on any other plan, click Workspace settings > Sources/Destinations.

2. Edit the entry for the connector you want to pin.

3. Set the Default Version to the version you want to use.

Self-managed plans: update the local connector image

If you self-manage Airbyte, you must manually update the connector image in your local registry before proceeding with the migration. Follow the steps below.

1. In the navigation bar:

   • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

   • If you're on any other plan, click Workspace settings > Sources/Destinations.

2. Find the connector you want to update in the list of connectors.

   note

   Airbyte lists two versions, the current in-use version and the latest version available.

3. Click Change to update your OSS version to the latest available version.

Update the connector version

Update each instance of the connector separately. If you have multiple instances of a connector, updating one doesn't affect the others.

1. In the navigation bar:

   • If you're on the Self-Managed Enterprise plan, click Organization settings > Sources/Destinations.

   • If you're on any other plan, click Workspace settings > Sources/Destinations.

2. Select the instance of the connector you wish to upgrade.

3. Select Upgrade.

4. Follow the prompt to confirm you are ready to upgrade to the new version.

Clear data from affected streams

After upgrading a connector with a breaking change, you must refresh affected schemas and clear your data.

1. In the nav bar, click Connections.

2. Find the connection affected by the upgrade.

3. Click the Schema tab.

4. Click Refresh source schema (looks like ). When Airbyte finishes, it shows you any detected schema changes.

5. Click OK.

6. Click Save changes

7. Clear the data for the streams affected by this upgrade.

Once the clear is complete, you can begin syncing your data again as usual.