The short answer
Google says your Local Services Ads performance reports will not transfer when the account moves into Google Ads, though lead history will. Before your wave, save each account's charged leads, spend and its call, message and booking split month by month: by screenshot or Google's promised download, through the Local Services API if you hold a manager account, or into a store such as DuckDive.
- The notice email gives you 14 days. For an agency with a dozen accounts, that is not enough. Start before it lands.
- No single method keeps everything. Plan on two of the three.
- File any lead disputes before your date. Google says manual disputes end with the move.
The migration timeline, wave by wave
Google's transition help page lays out three phases (as of November 2026). Find your row, then count back from it.
- August 2026. Select home and storefront service advertisers in the United States. Google names plumbing, HVAC, electrical, appliance repair, house cleaning, lawn care, roofing, pest control and moving.
- Late 2026. Broader groups, including service-area businesses with no storefront and accounts that use custom bidding or booking setups.
- 2027. Every account outside the United States, plus all the categories not moved in 2026.
"Select" is the word to notice in the first phase. Google did not take every advertiser in those trades in August, so a named category tells you that you are close, not that you are done. Roofing companies are on that first list too; a roofer still on the old dashboard should assume the next phase includes it.
Legal categories are not named in the August list, so multi-office law firms land in one of the later phases. Later is not safer. A firm with one account per office simply has more to capture.
How the notice works
The account administrator gets an advance email 14 days before the scheduled date, along with warning banners in the dashboard. A final reminder follows seven days later, and one more email confirms the move once it is done. If the admin on a profile left the business last year, nobody may see the first email at all.
The door closes on the day
PPC Land reports that once an account moves, logging in to the old Local Services dashboard sends you to the Google Ads campaign overview instead. Treat the migration date as the last day you can screenshot anything.
What moves to Google Ads and what does not
Google moves your setup and your customers. It drops the record of how the account performed. That split decides what you need to save.
| Data | Moves into Google Ads | Imported into DuckDive |
|---|---|---|
| Lead history: contacts, messages, older call recordings | Yes, onto the new Leads page | No, DuckDive does not read lead details |
| Charged leads by period | No, part of the performance reports | Yes, a count per account |
| Spend by period | No, past weekly spend is dropped | Yes, per account |
| Impressions and clicks | No | No; if your dashboard shows them, screenshot that view (Google's report help does not list them) |
| Ad-level reports | No | No |
| Call, message and booking split; credits | No, these live in the report screen | No |
| Settings: areas, service types, budget, schedule, photos | Yes, moved automatically | No, not a settings store |
Sources: Google Ads Help transition page and Google's LSA report help, checked November 2026.
Three changes on the far side affect how you will read your saved numbers later:
- Charged leads get a new name. In Google Ads they appear under Conversions, which Google describes as the total number of leads you were charged for.
- Weekly budgets become daily averages. Google divides the weekly figure by 7, and caps monthly billing at that daily average times 30.4.
- Manual bidding goes. Maximum cost per lead is no longer supported, and per-vertical target CPA gives way to one campaign-level target.
Save spend by calendar month, not by week, and your old figures will line up with what Google Ads bills you.
- Performance report
- The Reports view in the LSA inbox: charged leads, the call, message and booking split, total charged, credits, for the date range you pick. This is what does not migrate.
- Conversions (Google Ads, after the move)
- Google's label for the leads you are charged for once the campaign runs as Performance Max with a pay-per-lead goal.
Three ways to keep your performance history
Each option keeps a different slice. Pick by account count and by what you will ask of the history later.
| Question | Import into DuckDive | Export by hand | Local Services API |
|---|---|---|---|
| Suits | Several accounts, questions asked through an AI agent | One or two accounts | Agencies with a manager account and a developer |
| Charged leads and spend | Yes, per account | Yes | Yes, any date range |
| Calls by type | No | Yes, call, message, booking | Partly, phone calls and connected calls |
| Monthly impressions | No | Partly, if the screen shows them | No, last two days only |
| Needs a manager account | No | No | Yes |
| Work per extra account | Link it once | Every screen, again | None once the script runs |
| Askable later in plain English | Yes, up to 12 months per question | No, images and a sheet | Partly, after you load the files |
| The better pick when | You will compare accounts after the move | You need every figure for one account | You want raw monthly files you own |
Sources: Local Services API reporting guide and View reports on Local Services Ads, checked November 2026.
Most agencies need two of these: screenshots or the API for the complete archive, and DuckDive for the slice they will keep asking about.
Exporting by hand: what to download
Open the LSA inbox, select the menu at the top, then Reports. You can set the date range, and Google's report help says data exists only from October 1, 2017 onward. The report shows charged leads, the split by call, message and booking, total charged, credits received, and a filterable list of leads.
Google's report page does not mention a download button. The transition page says a download of historical reports will come "soon" on a redirection page, and until then tells advertisers who need their reports right away to take screenshots.
- Work one calendar month at a time. One wide range gives you a single total, and a single total cannot show you seasonality next spring.
- Get the date picker into every screenshot. An image without its range is useless in a year.
- Type the totals into one sheet as you go. Month, charged leads, calls, messages, bookings, total charged, credits.
- Finish with an all-time range. Add the monthly rows and check the sum against it. A gap means a month was skipped.
Skip the lead list. It moves to Google Ads with the account.
Pulling reports through the Local Services API
If your accounts sit under a manager account, Google's Local Services API can pull the same core numbers without a single screenshot. Every request to accountReports:search must include manager_customer_id; you can narrow it to one account with customer_id, separated by a semicolon. Dates go in as parts (startDate.year, startDate.month, startDate.day, and the same for endDate).
Each row comes back with the business name, currentPeriodChargedLeads, currentPeriodTotalCost, currentPeriodPhoneCalls and currentPeriodConnectedPhoneCalls, plus the previous period for each. Loop one month at a time from your oldest month to now and you get a clean monthly file per account.
Know what the API will not rebuild. Several fields are snapshots, not history:
impressionsLastTwoDayscovers only the last two days, so past monthly impressions are a screenshot job.averageWeeklyBudgetis one account-level figure, not a month-by-month record of what you ran.phoneLeadResponsivenessis a rolling figure for the previous 90 days.
Detailed lead reports are marked deprecated, capped at 31 days per request, and replaced by read-only resources such as local_services_lead in the Google Ads API, per its Local Services guide. Lead history migrates anyway, so most teams can skip them.
Run it early
Google's reporting guide does not say whether accountReports keeps answering for an account after it moves. Pull everything before the notice, not after.
Importing LSA history into DuckDive before your wave
DuckDive is where your AI agent reads marketing data from. Link an LSA account to its website and DuckDive imports that account's history and stores it, so questions run against DuckDive's copy rather than against the LSA report screen.
Each account keeps three numbers per window: leads, charged leads and spend. Your agent lines them up across every account you run, beside each site's Google Ads results. After the move, Google reports these leads as Conversions in Google Ads. Everyday LSA questions are on the Local Services Ads data source page.
-
Sign in with the Google login that manages the accounts
Use Continue with Google with the login your team already uses for LSA. Every LSA account it can see shows up for linking, next to that login's Analytics, Search Console and Ads accounts. If a client's account is not there, the client grants your login access in Google, then you look again.
-
Add a website for each LSA account
DuckDive organises everything by website, one LSA account per site. On an agency account, file each site under its client.
-
Link the LSA account, plus the site's other sources
Link each site's GA4 property and Search Console site, and its Google Ads and Local Services Ads accounts if it runs them. Linking starts the history import, which usually takes a few minutes; a long history can take longer.
-
Connect your agent, or let it do the setup
In Claude (any plan), ChatGPT (Business or Enterprise), Cursor or Claude Code, register
https://api.duckdive.ai/mcpas a remote MCP server and sign in with Google when the DuckDive page opens. There is no key. Each app files this under its own menu name, usually Connectors, Apps or MCP, and renames it often. For the agent to add sites and link accounts itself, connect from an admin login with "Also allow actions" left on.
Give your agent this lineSet up DuckDive for my website. Follow https://analytics.duckdive.ai/
agents.md -
Check every import before you trust it
Ask for
get_sync_statuson each site. For LSA it says ready, importing or failing, plus the date of the newest data. A failing LSA import a week before your date is the one thing worth a phone call.
Ask your agentWhich of my websites have Local Services Ads linked, and how recent is each one's LSA data?
Tools it calls list_websites get_sync_status
Which of our client sites have LSA linked, and is any of that data stale?
list_websitesfinds the 12 Saltmeadow client sites with an LSA account linkedget_sync_statusonce per site, for the LSA source
Ten of the twelve are ready, with LSA data through November 15. Two need attention before anyone relies on them.
| Site | LSA status |
|---|---|
| Brackwater Pest Control | Failing |
| Eelgrass Legal, Dover office | Importing |
| Quillbrook Electric | Ready |
| Nine other sites | Ready |
Brackwater has not imported since October 2. Ask the client whether your Google login still has access to that LSA account, restore it, then refresh. Check Eelgrass again tomorrow.
Once access is fixed, top up the recent weeks. A refresh pulls up to 30 recent days again, for LSA alone or every source on the site. Admins only, and each site accepts one refresh per quarter hour.
Ask your agentRefresh the last 30 days of LSA data for every website before our account migrates.
Tools it calls list_websites refresh_website_data get_sync_status
Get your LSA accounts imported before the notices start
Link each account to its website, then ask your agent which imports are ready and which are stale.
Free for 2 sites · No credit card
Worked example: an agency saving fourteen accounts
Saltmeadow Agency is made up for this page. It runs LSA for fourteen accounts: US home service clients, a three-office law firm and one Canadian client. Two accounts moved in August before anyone saved a report, and the agency rebuilt their history from invoices. Its plan sorts the rest by expected wave and gives each group an internal date that falls before its phase could plausibly begin.
| Group | Expected wave | Save by |
|---|---|---|
| Moved in August (Gullhaven Movers, Corbel Lawn) | Done | Too late; rebuilt from invoices |
| US home services still waiting, including Quillbrook Electric and Tern Point Roofing | Late 2026 | November 20 |
| Service-area clients with custom booking | Late 2026 | November 20 |
| Eelgrass Legal, three offices | Late 2026 or 2027 | December 5 |
| Canadian client | 2027 (non-US) | December 12 |
| Total: 14 accounts |
Google's late 2026 phase could already be running for some of those eight accounts, so they get the nearest date and nobody waits for a notice. The law firm could fall in either later phase, so it is treated as if it were the earlier one. For the twelve accounts still waiting, a junior screenshots monthly reports for the late 2026 group first, while the account lead asks the agent for a dated table per account.
Ask your agentFor each LSA account, give me leads, charged leads and spend for the last 12 months as a table I can save.
Tools it calls list_websites get_lsa_summary
A 12-month total hides the shape of the year, so for its biggest account the agency asks for every window and lets the agent subtract.
Ask your agentPull Quillbrook Electric's LSA numbers for the last 30 days, 90 days, 6 months and 12 months, then subtract to show the older half of the year on its own row.
Tools it calls search get_lsa_summary
Give me Quillbrook's year of LSA in one table I can file, with the older six months split out.
searchfinds the Quillbrook Electric website and its idget_lsa_summarylast 12 monthsget_lsa_summarylast 6 monthsget_lsa_summarylast 90 daysget_lsa_summarylast 30 days
Pulled November 16, 2026. The older half of the year is the 12-month totals minus the 6-month totals.
| Window | Charged | Spend |
|---|---|---|
| Last 12 months | 1,031 | $52,580 |
| Months 7 to 12 ago | 460 | $22,460 |
| Last 6 months | 571 | $30,120 |
| Last 90 days | 302 | $16,310 |
| Last 30 days | 95 | $5,320 |
The recent half carried more of the year: 571 charged leads against 460, up 24%, while spend rose 34%. Each charged lead cost more lately. Impressions and clicks are not in this data. If your dashboard shows impressions and clicks, screenshot that view too (Google's report help does not list them).
One habit follows from the table. Agent windows roll forward every day, so the 12-month view you pull in December no longer reaches November 2025. File each pull with its date, and the files add up to a longer record than any single question returns.
Last, the agency checks which LSA sites have no Google Ads account linked yet, since the client's Google Ads account is where Google will show those leads once the campaign moves. The ad spend versus leads ledger shows how to keep LSA and Google Ads leads in one view without counting a lead twice.
Ask your agentList our websites that have an LSA account linked but no Google Ads account linked yet.
Tools it calls list_websites
A pre-migration checklist
Run this per account. Tick an item only when the file exists, not when it is planned.
Before each LSA account moves
- Admin email checked. The person listed as administrator still reads that inbox and knows to forward the notice.
- Wave guessed and dated. Category and country point to a phase; your internal deadline sits well ahead of the earliest date that phase could start.
- Monthly report screenshots. One per calendar month back to the account's start, date picker visible.
- Totals sheet. Month, charged leads, calls, messages, bookings, total charged, credits, checked against an all-time total.
- Dashboard views captured. If your dashboard shows impressions and clicks, screenshot that view too (Google's report help does not list them). Neither the API nor DuckDive returns past monthly impressions.
- API pull, if you have a manager account. One file per account per month, run before the notice.
- DuckDive import ready. The LSA source shows ready and recent, refreshed for the last 30 days.
- Disputes filed. Anything you meant to dispute is in before the date.
- Settings noted. Weekly budget, bid mode and maximum per lead written down, since bidding rules change on the far side.
What DuckDive will not save for you
DuckDive keeps a narrow slice. Know the edges before you count on it as an archive.
- Only leads, charged leads and spend. No impressions, clicks, credits, or the call, message and booking split.
- No lead records. It does not read contacts, messages or recordings, and it cannot dispute anything.
- Twelve months per question. The longest window an agent can ask for is the last 12 months, and dates are fixed windows, not custom ranges.
- No settings. Budgets, bids, service areas and schedules are not stored.
- No Google files. When Google's download appears, fetch it yourself.
So when is it the wrong tool? If you have one account and your notice already arrived, spend the afternoon on screenshots. If you need every metric Google ever showed you, the hand export is the only complete record. DuckDive earns its place when you run several accounts and want to keep asking about them next to each site's other Google data. For trades with many service-area accounts, the home services page shows how that looks day to day.
Before your migration notice arrives
- Agree who forwards notices. An agency that relies on clients to pass on Google's email should settle that in writing now.
- Settle open disputes. Manual lead disputes are not supported after the move, according to Google's transition page.
- Freeze a baseline. Write down the last full month's charged leads and spend per account. That is your reference for the first month in Google Ads.
- Brief the client. Tell them reports will look different, charged leads will be called conversions, and budgets will read as daily averages.
Do the slow part first: screenshots. Linking a site in DuckDive is done once, and the import then runs on its own.
Questions LSA advertisers ask about the move
Will my Local Services Ads reports move into Google Ads?
No. Google's transition page says LSA performance reports will not transition, and past impressions, clicks, weekly spend and ad-level reports will not migrate. Save them before your date, as of November 2026.
Do my leads and call recordings move?
Yes. Google says past lead history, including contact details, message history and older call recordings, transfers to the new Leads page in Google Ads. That is why the lead list is the one part of the old dashboard you can skip saving.
When will my account migrate?
Google lists select US home and storefront services from August 2026, broader groups such as service-area businesses in late 2026, and non-US accounts plus remaining categories in 2027. The account administrator gets an email 14 days before the scheduled date.
Can I download my LSA reports as a file?
Not yet, as of November 16, 2026. Google says a download of historical reports will come soon on a redirection page, and tells advertisers who need reports right away to take screenshots. The Local Services API is the other route if your accounts sit under a manager account.
Can I still open the old LSA dashboard after I migrate?
Plan as if not. PPC Land reports that logging in on or after the migration day sends you to the Google Ads campaign overview instead. Anything you have not captured by then is out of reach on that screen.
Can a single business use the Local Services API?
The reporting guide builds every account report query around a manager account ID, so in practice it suits agencies and businesses that manage accounts through a manager account. A single business with one account is usually faster with screenshots.
How far back can my agent read LSA data in DuckDive?
Each question can cover up to the last 12 months, in fixed windows of 7, 14, 30 or 90 days, 6 months or 12 months. Save each pull with its date if you want a record that outlasts the rolling window.
Sources
- Local Services Ads transition to Performance Max campaigns with pay-per-lead goals, Google Ads Help Center, checked November 16, 2026.
- Google folds Local Services Ads into Google Ads, cuts historical reports, PPC Land, checked November 16, 2026.
- View reports on Local Services Ads, Local Services Help, checked November 16, 2026.
- Local Services API: Reporting, Google Developers documentation, checked November 16, 2026.
- Local Services campaigns, Google Ads API documentation, checked November 16, 2026.
Last reviewed . Numbers in EXAMPLE DATA blocks are fictional.
