Where Your Old LSA Reports Go After Migration

Historical Local Services Ads campaign performance reports do not move into Google Ads. Google says the old dashboard becomes inaccessible after migration, so the advertiser's tested export becomes the continuing record. Google's LSA migration announcement states that past customer lead history transfers to Lead Manager and new campaign reporting begins in Google Ads.

That split explains most post-migration confusion. An old customer conversation can exist in Lead Manager while the report showing the period's spend, charged-lead total, lead categories, and credits remains absent. A new Google Ads campaign can show current Cost and Conversions without carrying the old report timeline forward.

Treat the migration as a reporting boundary. Save the old performance record, verify the transferred lead history, and label the date when new Google Ads reporting starts. Keep the three records connected through Customer ID, business or location, date range, and metric definitions.

The advertiser keeps the historical campaign report as a downloaded file. Google moves past customer lead history to Lead Manager and starts new campaign reporting inside Google Ads. Google also intends to transfer campaign settings and assets, which the advertiser must verify. The linked Google Business Profile supplies core business identity details.

Google Ads Change history begins a new audit trail for supported edits made after migration. It can help explain a later budget, targeting, status, or bidding change. It cannot recreate an old performance period or establish the pre-migration value of every LSA setting.

Use this transfer map during the first review. Assign one owner and completion test to every destination instead of asking whether all LSA data transferred as one package.

Google's Local Services Ads report guide documents the historical report fields and says advertisers can access report data from October 1, 2017 onward. The exact history for one account depends on when it began advertising and the data present in its report.

Save the raw report before combining it with CRM or booking data. Add an equal-period baseline and a year-over-year or seasonal period when reliable history exists. Open the downloaded file and confirm the date range, account, fields, and totals. A download that cannot be located or opened is not a usable archive.

Keep business outcomes in a separate table keyed to the same period. Operational systems provide qualified leads, bookings, completed jobs, revenue, cancellations, and repeat-customer data. Label the source and definition for each field.

Use a stable filename: CustomerID_BusinessOrLocation_StartDate_EndDate_ExportDate. Keep a raw copy, a working copy, and a short README or worksheet that explains the account time zone, report filters, lead definitions, and known data gaps.

Store the archive in company-controlled storage. Restrict files with customer contact details or call data according to the business's existing access and retention policies. A campaign report and a customer-record export can require different permissions.

Agencies should maintain an archive register with one row per account and period. Include Customer ID, client, location, notice date, migration date, export owner, file path, date ranges, open-test status, and authorized backup owner. Avoid placing passwords or personal customer data in the register.

Open Goals, select Conversions, and then Leads to reach Lead Manager. Google says past customer leads transfer there, including contact details, message history, and older call recordings. The table can show lead type, charged status, customer information, feedback, and permitted download controls.

Verify the Customer ID and business before reviewing records. Confirm the people responsible for calls, messages, booking, lead feedback, and CRM export have the correct access. Google's Local Services lead-management guide explains the existing LSA lead workflow, including inbox review, call handling, messages, and booked-job updates.

Lead Manager preserves customer-level history. It does not provide the old campaign report's continuous spend and performance record. Reconcile lead counts across the migration boundary with date ranges, charged status, lead type, time zone, and export timing before labeling rows as missing or duplicated.

Open the migrated campaign dashboard and record the first date with post-migration data. Google directs advertisers to Conversions, Cost, and Cost per conversion. In this specialized campaign, Conversions means charged leads. Keep that definition in the report header.

Use Google Ads reporting for the new platform period and create a saved report with Customer ID, campaign, date, Conversions, Cost, and Cost per conversion. Add lead or conversion segments when the team understands their definitions and the interface makes them available. Keep the report name consistent across locations.

Google Ads report scheduling documentation explains how authorized Google Ads users can save and schedule reports. Use a company-controlled recipient list, review access before adding customer data, and test the delivery. The scheduled report is a forward-looking control; it cannot fill the old performance history.

Open Campaigns > Change history to review supported Google Ads edits after migration. Filter by date, user, campaign, or change type when investigating movement. Google Ads Change history documentation documents the available review workflow.

Place Change history beside the performance report. Record the editor, field, old value, new value, reason, and review date for each material correction or optimization. Link support case numbers in the internal record when a support-assisted change affects the campaign.

Keep the boundary explicit: the old LSA report describes pre-migration performance, Lead Manager holds customer lead history, the new Google Ads report describes post-migration performance, and Change history explains supported edits made in the new system.

Choose a pre-migration window that ends before the platform move and a post-migration window that begins after the move. Use equal lengths and matching weekdays. Add a transition label for migration day and any stabilization period rather than blending it into both windows.

Compare charged leads, cost, and cost per charged lead with the same definitions. Add qualified leads, booked jobs, completed jobs, revenue, and cancellations from the same business systems used before migration. Record season, weather, staffing, operating hours, promotions, service mix, and capacity when they changed.

A complete comparison can still have limitations. Small lead counts, delayed job completion, changed definitions, missing old exports, or an operational change can prevent a causal conclusion. State the limitation next to the result and keep monitoring with the same method.

Agencies with an approved technical workflow can review supported Local Services reporting resources in the Google Ads API documentation for Local Services campaigns. Google documents Local Services lead and conversation resources alongside verification, license, insurance, and employee reporting resources.

Field availability depends on API version, account type, permissions, migration status, and Google support. Use an API export to complement the tested human-readable archive and approved CRM record. Do not use it to claim that Google transferred the old campaign report.

Keep credentials outside spreadsheets and repositories. Limit exported customer data to the people and systems authorized to handle it, and follow the business's existing retention policy.

Google's announcement does not provide a self-service restoration path for historical campaign performance reports after the old dashboard becomes inaccessible. Preserve the report before migration and test the file. Use signed-in support for an account-access, missing-campaign, permission, or transfer issue.

Describe a support request with the Customer ID, business or location, notice date, migration date, expected record, found record, evidence, and business impact. Avoid sending passwords or unnecessary customer data.

A support representative may help investigate a migration issue. Keep the archive plan independent of that possibility because lead history in Lead Manager and a support case do not recreate the old report timeline.

Source review completed July 29, 2026. Report-transfer rules, Lead Manager destination, new campaign metrics, transferred settings, and dashboard access changes come from Google's LSA migration announcement. Historical report fields and the October 1, 2017 availability date come from Google's Local Services Ads report guide.

Lead-handling details come from Google's Local Services lead-management guide. Post-migration audit-trail guidance uses Google Ads Change history documentation. Report scheduling uses Google Ads report scheduling documentation. The archive register, source bridge, comparison table, and ownership process are PrimeLSA operating recommendations.