How to Download LSA Reports Before Google Ads Migration

Start by opening the current Local Services Ads inbox, selecting the menu, and opening Reports. Choose a complete date range and record the account, dates, filters, and totals. Google says a dedicated historical-report download page will be available soon from the post-migration redirection page; advertisers who need the reports immediately should capture them before migration.

Google's LSA migration announcement says previous campaign performance reports will not carry into Google Ads. Past customer lead history follows a separate transfer path into Lead Manager, so transferred calls and messages do not recreate the old campaign-performance timeline.

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.

Other migration guides tell advertisers what they should manually download. Advantage maintains the core baseline automatically and keeps refreshing it weekly while the legacy campaign remains available. Migration Data can be downloaded for the current account or every active account the user manages.

The feature is included with Advantage at no additional cost. The download combines independently maintained PrimeLSA reporting history with account configuration and verification snapshots that are not available together in one standard legacy LSA dashboard export. Open Advantage by PrimeLSA to review the broader account-intelligence workflow.

Each archive includes a manifest that states the account, covered periods, field definitions, known gaps, and included files. Bulk downloads identify accounts whose archive is still being prepared instead of representing missing records as zero.

On one active PrimeLSA account, Migration Data preserved more than 1,000 days of daily performance history, hundreds of days of lead outcomes, 10 services, 25 service areas, bidding configuration, and verification snapshots.

Those figures describe one account, not a universal product minimum. Actual coverage varies with campaign age, legacy campaign dates, connected-account history, locally retained lead data, and whether a field is available for that account.

Charged CPL appears only where PrimeLSA has authoritative charged-lead coverage for the same account day. Google's rolling 90-day phone-responsiveness history begins when PrimeLSA first captures it; the value is not backfilled for earlier dates.

Migration Data does not fabricate fields that cannot be supported. It does not provide service-level spend or CPL, ad-level performance, business photos, or callout assets. Owners should preserve those assets separately when they need them.

Customer contact details, verification documents, document links, raw provider payloads, and message and call content are intentionally excluded. The archive uses aggregate lead outcomes and controlled verification fields to preserve useful history without creating a second customer-communication store.

The correct claim is that PrimeLSA preserves its independently maintained historical reporting and account snapshots. It does not mean Google's old campaign report transfers into the new Google Ads campaign.

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.

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 when one appears. Google says a dedicated historical-report download page will be available soon from the redirection page. Preserve structured rows when offered. If the report is needed immediately and no download is available, capture the complete report view and its date and filter context before migration.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Source review completed September 7, 2026. Report continuity, dashboard access, lead-history transfer, Lead Manager location, new campaign metrics, the planned historical-report download page, and Google's immediate screenshot guidance 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. PrimeLSA Migration Data claims were checked against the production implementation and an account archive generated September 7, 2026. The manual archive set, file naming, privacy-safe checklist, QA process, and recovery sequence are PrimeLSA operating recommendations.