Quick answer
Save the historical report before access ends, then prove the archive works
Before your LSA account migrates, save dated performance reports and the account context needed to interpret them. Google says previous campaign reports will not transfer into Google Ads, although past customer lead history moves to Lead Manager. Use the report controls available in your account, test each saved file, and keep private lead records in approved storage. Sources reviewed July 31, 2026.
What this covers
- Save performance reportsPreserve complete date ranges, charged leads, spend, lead-type breakdowns, credits, and available lead records before dashboard access ends.
- Capture account contextRecord services, areas, schedule, budget, bidding, photos, routing, access, and operating conditions on the same date.
- Test the archiveOpen every file, confirm its account and period, assign an owner, and make sure a second authorized person can find it.
Pre-migration archive
Build an LSA archive another reviewer can use
Google says old campaign reports will not carry into the migrated campaign. Save the performance record, lead context, and settings as separate evidence bundles.
Performance reports
Save complete periods with charged leads, spend, lead types, credits, filters, and the account identity.
Lead review
Retain only permitted lead-review information and keep customer records in restricted approved storage.
Settings and context
Capture services, areas, schedule, budget, bidding, photos, routes, access, staffing, season, and source notes.
Save the report record before the old dashboard becomes inaccessible
Download LSA reports before migration by opening the current Local Services Ads inbox, selecting the menu, and opening Reports. Choose a complete date range and use the save, download, export, or print control available in that account. Google does not publish one universal export-button label for every pre-migration report view.
Google's LSA migration announcement says previous campaign performance reports will not carry into Google Ads and instructs advertisers to download, export, or manually save the data before migration. Past customer lead history follows a separate transfer path into Lead Manager.
Save report data, lead-review records, account settings, and business context as separate files. Test the files before dashboard access ends. A filename and manifest should identify the account, source, exact period, filters, owner, and privacy classification.
Download nine report and context records
Build the archive with nine evidence groups. Use the first five for performance and lead review. Use the last four for account and operating context that does not appear in campaign reports.
Google's report guide lists charged leads, Category or Direct Business Search filters, calls, messages, bookings, amount charged, spend breakdowns, a filterable lead list, and lead credits. The business supplies qualification, booked outcomes, completed work, and revenue from its approved systems.
Save aggregate records where they answer the question. Store customer contact details, messages, and recordings only when the business has authority and a documented need. Keep those records out of public screenshots and general shared folders.
| Archive item | Record | Source |
|---|---|---|
| 1. Period reports | Monthly, 28-day, 90-day, year-to-date, seasonal | LSA Reports |
| 2. Spend and charged leads | Totals and cost per charged lead | LSA Reports |
| 3. Category and lead type | Category, Direct Business Search, calls, messages, bookings | LSA Reports |
| 4. Feedback and credits | Visible feedback, charged state, and credit amount | LSA lead and report views |
| 5. Lead context | Permitted call, message, and booking records | LSA lead inbox |
| 6. Services | Business categories, services, and job types | Account settings |
| 7. Locations | Targeted areas and service-area setup | Account settings |
| 8. Campaign controls | Budget, bidding, schedule, photos, profile, routing, access | Settings and account records |
| 9. Business context | Staffing, promotions, season, capacity, prices, known changes | Manager note and business systems |
Save the current LSA performance report step by step
Sign in to the Local Services Ads account named in the migration notice. Confirm the business, Customer ID or account identifier, profile, administrator, currency, and time zone before selecting any dates.
Open the Local Services Ads inbox. Select the menu at the top, then select Reports. Choose a complete and explicit date range. Record the visible filters, including Category or Direct Business Search and lead type where the account offers them.
Use the report's available save control. Google tells advertisers to download, export, or manually save their data, while the help page does not name one file control for every account state. Preserve structured rows when offered. Use print or screenshots for supporting context when no structured option appears.
Repeat the process for each planned period. Open every file, check that it contains data, and add the exact start and end dates to the filename or manifest before signing out.
- Confirm the scheduled account and profile.
- Open Inbox > Menu > Reports.
- Select a complete date range and record active filters.
- Use the save or export control that appears in the account.
- Repeat for each comparison period.
- Open the saved result and confirm its account, dates, rows, and totals.
Save overlapping date ranges for different decisions
Save the previous complete calendar month for month-over-month operations. Save the last complete 28 days for an equal-weekday migration comparison. Save the trailing 90 days for service and lead-mix context. Save year to date for finance and management continuity.
Seasonal businesses should add the same period from the prior year or another comparable demand window. Use the date range that the business can defend and note weather, promotions, staffing, price, territory, and capacity changes.
Google's Local Services Ads report guide says LSA report data is available from October 1, 2017 onward. A long-running account can test the earliest useful period, but it does not need to create an unreadable archive of every overlapping date if the business has no use or retention basis for it.
| Period | Primary use | Filename field |
|---|---|---|
| Previous complete month | Routine monthly comparison | YYYY-MM-DD_to_YYYY-MM-DD |
| Last complete 28 days | Same weekday mix before and after | pre-migration-28-days |
| Trailing 90 days | Service, lead-type, and cost context | trailing-90-days |
| Year to date | Management and finance continuity | year-to-date |
| Comparable prior period | Season or demand context | prior-year-comparable |
Keep report exports, lead history, and business outcomes separate
Use historical campaign reports and customer lead history for different questions. Use the report for period totals, spend, charged leads, filters, lead types, and credits. Use Lead Manager for contacts and conversations. Use a business outcome system for qualification, booking, completion, and revenue.
Google transfers past customer lead history into Lead Manager. Google does not carry the old campaign performance report into the new campaign. An old caller may appear after migration while the former period report remains unavailable.
Keep each source labeled. Joining rows without a source, period, account, and stable identifier can produce duplicate leads or false totals. Preserve raw files unchanged and build comparisons in a separate working copy.
| Save now | Expected after migration | Reason |
|---|---|---|
| Historical campaign performance reports | Do not transfer | Preserve the old cost and charged-lead baseline |
| Dated settings and context | Transferred settings need review | Prove what should have moved |
| Permitted lead-review records | Past lead history transfers | Verify contacts and conversations |
| Business outcome exports | Remain in business systems | Connect leads to qualified and booked work |
| New Google Ads reports | Begin after migration | Build the new reporting timeline |
Put the minimum LSA metrics in the baseline
Record the report date range, spend, total leads, charged leads, lead type, credits, and cost per charged lead. Add Category or Direct Business Search, service line, location, and account when those fields or filters are available.
Use business systems for qualified leads, booked jobs, completed jobs, approved revenue measures, answer status, and message handling. Write one definition for each measure and keep the same date basis across the comparison.
A blank denominator means the rate is unavailable. Zero means the business measured no outcomes. Keep those states separate in the worksheet so a missing booking feed does not look like a zero-percent booking rate.
| Metric | Preferred source | Definition note |
|---|---|---|
| Spend | LSA report | Ad charges in the explicit period |
| Charged leads | LSA report | Leads charged by Google |
| Cost per charged lead | Spend / charged leads | Use the same period and account scope |
| Lead type | LSA report or lead inbox | Call, message, booking, or supported type |
| Qualified lead | Business intake system | Written fit and intent rule |
| Booked job | Booking or dispatch system | Written booking rule |
| Completed job and revenue | Operations or accounting | State the completion and revenue date basis |
| Answered or missed call | Approved phone system | Use one answer-status definition |
Use a filename and manifest that survive staff turnover
Use a filename that works without opening the file: YYYY-MM-DD_business_account_period_report-type. Include the export date first, then a privacy-safe business or location label, account identifier, period, and record type.
An example is 2026-07-31_acme-hvac_1234_trailing-90-days_lsa-performance.csv. Replace the business name in public or vendor-shared copies when the distribution does not require it.
Number the folders to preserve the archive order: 01-performance-reports, 02-lead-review, 03-account-settings, 04-context-notes, and 05-post-migration-reports. Keep a manifest at the archive root.
| Manifest field | Example | Purpose |
|---|---|---|
| Account and Customer ID | Acme HVAC / 123-456-7890 | Prevents cross-account joins |
| Source system | Old LSA | Separates old and new reporting |
| Extract date | 2026-07-31 | Records when an authorized user saved the file |
| Performance period | 2026-05-01 to 2026-07-29 | Defines the data window |
| Time zone | America/Los_Angeles | Keeps day boundaries consistent |
| Filters and metrics | Category; calls; charged leads; spend | Preserves the report definition |
| Known missing fields | No export for booking notes | Prevents false completeness |
| Owner and privacy class | A. Manager / Restricted | Assigns custody and access |
Test every export before calling the backup complete
Open the file with the application your team will use later. Confirm that the date range appears in the content or filename, the account is identifiable, the expected rows or totals exist, and formulas do not replace raw values.
Move the file into approved storage and record the owner. Ask a second authorized person to find it, open it, identify the account and period, and explain the key fields without help from the person who created the archive.
A screenshot can support the record, but use a structured export when the account supplies one. Store caller details, messages, and recordings under the business's privacy and retention controls. Do not place customer data in the downloadable checklist.
- The file opens without an error.
- The exact date range is visible in the file or filename.
- Confirm the business and account identity.
- The expected rows, totals, filters, and metrics are present.
- Record the approved storage location and file owner.
- A second authorized reviewer can find and interpret the file.
Build a separate Google Ads report after migration
After migration, open the pay-per-lead campaign statistics table. Add Conversions, Cost, and Cost / conv., then set an explicit date range. Use only filters or segments that return useful data for the specialized campaign and preserve the table definition.
Google Ads report scheduling documentation says Google Ads statistics tables can download Excel CSV, TSV, PDF, XLSX, XML, or Google Sheets where offered. The same control can schedule a report for account users with the required direct access. Google removes saved reports after more than 18 months without access, so keep an external archive copy.
Use Google Ads Report Editor documentation for a custom table or chart when the campaign table does not answer the question. Keep new Google Ads reports in 05-post-migration-reports and do not overwrite the old LSA files.
Archive multi-account reports with an account-level register
Agencies should keep one archive register across client accounts. Include Account, Customer ID, business, location, migration date, source system, report period, time zone, owner, storage path, status, and exception note.
Google Ads manager-account report documentation documents manager-account reports, account dimensions, explicit date ranges, comparison controls, downloads, and schedules. Select only the migrated client accounts for a new Google Ads report and include Account and Customer ID in each row.
Keep pre-migration LSA exports in a separate historical dataset. Map old charged leads, spend, lead types, and credits to the new metric definitions before joining files. A common column label does not prove that the source, denominator, or account scope matches.
Recover available records if the account already migrated
Open the migrated campaign in Google Ads and record its start date, status, budget, bidding, services, areas, schedule, assets, and Business Profile connection. Use Goals > Conversions > Leads for transferred customer lead history.
Search approved CRM, call-tracking, booking, accounting, agency, inbox, and scheduled-report archives. Ask authorized users whether they saved monthly summaries or board reports. Label each recovered file with its source and limits.
Google does not document a self-service restoration path for the old campaign report after dashboard access ends. Build a dated post-migration baseline and avoid reconstructing exact historical numbers from memory or isolated screenshots.
Complete the final pre-migration report check
Finish the pre-migration archive with reports for several useful periods, reviewed lead history, a dated settings capture, business outcome records, tested files, approved storage, a named owner, and a second-person recovery check.
Schedule the migration-day account check and the Day 7 operational review. Use Day 14 for a directional performance check after Google's stated ramp window, then start a 28-day post-transition comparison.
- Reports cover monthly, 28-day, 90-day, year-to-date, and seasonal needs.
- The archive distinguishes reports, leads, settings, and business outcomes.
- Every file opens and identifies its account, source, period, and filters.
- Customer records use approved restricted storage.
- Name the owner and second reviewer.
- Schedule Day 0, Day 7, Day 14, and post-transition reviews.
Source, interface, and privacy note
Source review completed July 31, 2026. Report continuity, dashboard access, lead-history transfer, Lead Manager location, new campaign metrics, and the instruction to download, export, or manually save historical reports come from Google's LSA migration announcement.
Old LSA report fields, navigation, filters, and the October 1, 2017 availability date come from Google's Local Services Ads report guide. New Google Ads formats and scheduling come from Google Ads report scheduling documentation. The archive set, manifest, file naming, privacy-safe checklist, QA process, and recovery sequence are PrimeLSA operating recommendations.
Editorial note
Written by Arthur Z and last updated August 5, 2026. PrimeLSA keeps public guidance practical, Google Local Services Ads-specific, and connected to real account review.
