Amazon Ads deletes its old reports on January 31. Find the dashboards that still depend on them before December 17
Somewhere a scheduled Amazon Ads report lands in an inbox every Monday, gets pasted into a sheet, and feeds a chart someone shows the boss. Amazon is switching that report off in January, and the sheet won't notice until it's empty.

Amazon Ads is closing its legacy sponsored ads and Display, Video and Audio report pages: they become read-only on December 17, 2026, and on January 31, 2027 every remaining saved report, schedule and historical file is deleted. Before December 17, list every scheduled report, trace where its file goes, migrate it to unified reporting, compare old and new columns, and download the history you need, including the ten report types that can't move yet.
The Monday report
In a lot of businesses that advertise on Amazon, there's a report nobody thinks about. Every Monday a scheduled file from Amazon Ads arrives in someone's inbox. They paste it into a spreadsheet, or a connector picks it up, and it feeds a chart that gets shown in a meeting. It has worked for two years. Nobody remembers who set it up.
That report is on a clock. According to an Amazon Ads Support Center page updated on November 12, as reported by PPC Land, Amazon is closing its two legacy reporting pages: the sponsored ads reports page and the Display, Video and Audio campaigns reports page. From December 17, 2026, they become read-only: you can't create or edit reports there. On January 31, 2027, "all saved reports, scheduled reports, and historical data still on these pages will be permanently deleted." Amazon adds that the dates "are subject to change."
The original shutdown date, set in June, was December 31. It moved a month later, and gained a deletion step and a read-only phase along the way.
Count the reports, then follow each one
The report isn't the thing that breaks. The sheet that expects it every Monday is.
So the first job isn't migration. It's a census. Open both legacy report pages in every advertising account you run and list every saved and scheduled report. For each, write down who receives it and how. Then follow it to where it ends up: a spreadsheet, a script, a connector into a dashboard tool, a client report your agency builds. Note which columns that destination actually reads, and who would notice if it stopped.
This takes an afternoon for a small account and longer for an agency with many clients. It's worth it, because the next step changes the columns.
How the work moves
Trace one report to where it ends up
- Report
Name, type, account and schedule, from the legacy reports page.
- Delivery
Who receives the file, by email or download, and how often.
- Destination
The sheet, script, connector or client deck that uses it.
- Columns
Which fields that destination actually reads.
- Owner
The person who notices if it stops.
The report isn't the thing that breaks. The sheet that expects it every Monday is.
What the migration tool won't carry
Amazon has offered a self-service migration tool since September. You start it from a banner on the legacy page, confirm, and a status table shows what moved and what failed. Migrated reports appear in unified reporting, Amazon's newer reporting system.
The tool has limits, and Amazon lists them. It only moves "active saved or scheduled reports within the last 24 months." Some legacy fields have no equivalent in unified reporting and are simply left out. Some metrics are dropped because the levels don't match: Amazon's example is top-of-search impression share, which legacy reports show by keyword, targeting and campaign, but unified reporting shows only by campaign.
Then there are ten report types that "aren't available yet in unified reporting": the pricing transparency report, conversion path report, Amazon Attribution report, Sponsored Products retailer dimension, Sponsored Products and Sponsored Brands prompt reports, Sponsored Products Video report, industry standard report, benchmark report, Sponsored Products budget report, and the Amazon Business Sponsored Products placement report. Amazon hasn't given dates for any of them. If you rely on one, download its history from the legacy page before January 31, and plan for a gap.
Compare old and new, column by column
A migrated report that arrives with fewer columns looks fine until a formula returns zero. So before you switch any destination over, put an old file and a new file side by side for the same week. Check every column the destination reads. Check the names, since a renamed column breaks a lookup as surely as a missing one. Check totals for spend, sales and clicks against each other.
Small differences may come from how the two systems count, and are worth writing down rather than chasing. Large ones usually mean a filter, a date range or a time zone setting didn't carry over.
Where a column is gone, decide what replaces it: a different metric, a different level, or a note in the dashboard saying the series ends here. Then change the spreadsheet, script or connector to read the new file, and keep the old one running alongside for a week or two if you can.
Two more things worth knowing. PPC Land notes the page doesn't say whether scheduled reports keep delivering during the read-only period, so don't count on the old schedule running to the end of January. And if you pull reports through the Amazon Ads API rather than the console, that page doesn't cover it; check your connector vendor's plans separately.
Don't move everything
A census usually turns up reports nobody reads. A schedule set up for a campaign that ended, a weekly file sent to someone who left, three versions of the same search term report for three people. Migrating them all just creates new things to maintain.
So give each report one of three marks. Keep it, if something real depends on it. Merge it, if two or three reports do the same job and one well-designed report would serve everyone. Drop it, if nobody can say who uses it. For the dropped ones, tell the recipients before December 17 rather than letting the file simply stop arriving.
History is a separate question from schedules. If you rely on last year's numbers for year-over-year comparisons, seasonal planning or client reporting, download what you need from the legacy pages before January 31. Don't assume the new system will show the same history, in the same shape, for the same campaigns. Save the files somewhere the whole team can find, with a note on what each one is.
Sequence of work
Backward from deletion day
- Now - Dec 10
Census done, migration run, history for the ten unsupported types downloaded.
- Dec 17, 2026
Legacy pages go read-only. No new reports, no edits.
- Jan 1, 2027
DVA display ads on Amazon's store pages counted only once on screen; a break in the series.
- Jan 17, 2027
Amazon's 14-day deletion warning begins.
- Jan 31, 2027
Legacy reports, schedules and history deleted.
Work backward from January 31
Aim to finish the census, the migration and the history downloads by around December 10. That leaves a week before the pages lock, in the busiest weeks of the year, when you won't want to be rebuilding reports.
January has a second break in it. From January 1, Amazon counts impressions for Display, Video and Audio display ads on its own store pages only once the ad appears on a shopper's screen, and PPC Land reports Amazon expects about 63% fewer on average. If you compare December to January in DVA, you'll be looking at a new counting method and a new reporting system in the same month. Write that on the chart before someone asks why impressions collapsed.
Reports that feed other systems are automation, even when nobody calls them that. Finding them, rewiring them and making sure someone owns them is part of our business automation work. Talk to us.
Related work: Sutton|Place
We build alongside the people doing the work.
Bring us the problem you’re thinking about.