HVAC LSA Migration: What Owners Should Save

Google lists HVAC in the first U.S. Local Services Ads migration phase beginning in August 2026. That first phase covers select home-services advertisers with a physical storefront. The later 2026 phase includes additional groups, such as service-area businesses without a storefront and accounts using certain custom bidding or booking setups. Google's LSA migration announcement remains the source for the current rollout description.

The broad phase date does not replace the account-specific deadline. Google says the listed administrator receives an email 14 days before migration, the old dashboard shows a banner, and a final reminder follows seven days later. Save the notice date, migration date, Customer ID, account time zone, administrator, archive owner, and Day 1 reviewer in one record.

HVAC accounts need more than a generic export because season, service mix, weather, technician capacity, and after-hours coverage can move together. A single cost-per-lead average cannot explain whether the account produced cooling repair, furnace work, maintenance calls, replacement opportunities, or requests outside the service area.

Open the existing LSA Reports view before the migration date. Save a recent operating period, the preceding equal-length period, and a year-over-year period when the account has reliable history. Add a peak cooling or heating period if the normal comparison window misses the season the business is entering.

Name each file with the Customer ID, business or location, start date, end date, and export date. Open the saved file after download and confirm it contains the expected account, period, columns, and totals. Keep an authorized local or company-controlled copy because the former LSA report will not remain available after migration.

Google's old report can include charged leads, lead category, Direct Business Search or Category attribution, call, message, or booking type, total charged amount, credits, and advertiser-entered booked-job details. Preserve the raw export before cleaning, combining, or adding CRM data.

Create one row for each service line with a stable business definition. A practical HVAC file may include cooling repair, heating repair, preventive maintenance, installation or replacement, emergency service, and indoor-air work. Use the services offered and selected in the account. Keep the definitions stable across each comparison period.

For each service line, record Google charged leads and spend beside business outcomes from the CRM or dispatch system. Useful operating columns include qualified leads, booked jobs, completed jobs, revenue, cancellation count, average ticket, and available appointment capacity. Label the source of every column. Google conversions, dispatcher bookings, and completed paid jobs are different records.

Reconcile the service-line rows to an account total. If dispatch data does not support a repair and replacement split, keep the broader category and write down the limitation. A blank cell with a source note is more useful than an estimated number presented as fact.

Add context that the platform report cannot supply. Record heat waves, cold snaps, storms, smoke events, holidays, office closures, technician shortages, extended hours, and promotions when they affected the selected period. Use a short dated note and a source, such as the dispatch calendar or staffing plan.

Capacity belongs beside demand. Ten additional leads during an open schedule can carry a different business value than ten leads during a week with no open appointments. Record open appointment slots, after-hours coverage, and any temporary service-area restrictions. Keep that context with the baseline so the post-migration reviewer does not attribute each change to the new interface.

Use the same calendar boundaries for the Google report and the operating data. If revenue lags the lead date because a replacement job closes later, keep a lead-date view and a completion-date view instead of shifting one source until the totals appear to match.

Record the current weekly budget, bid mode, and each service-level target before migration. How LSA bidding works explains the current LSA controls and the difference between a budget and a bid target. Google says the migrated campaign will show a daily average budget calculated from the prior weekly average divided by seven. Its monthly spending limit equals that daily average multiplied by 30.4.

Google is also retiring manual bidding and vertical-level Target CPA controls in favor of a campaign-level target. Separate campaigns remain an available structure when different service groups require different bidding rules. Preserve the old targets, lead value, close rate, average ticket, margin context, and capacity before deciding whether the HVAC categories belong together.

Google has not published a formula that combines several old vertical targets into one new campaign target. Treat any blended number as a planning calculation. Record the weights, date range, and source so another reviewer can reproduce it.

Save screenshots or a dated worksheet for selected services, service areas, exclusions, ad schedule, phone routing, and message ownership. Google's LSA service-area and job-type guide explains the existing service-area and job-type controls, while Google's LSA ad-scheduling guide describes all-day, business-hours, and custom schedules.

The transferred campaign can be accurate while the operating handoff still fails. Place a test call through the approved path, confirm the destination number, check voicemail and overflow behavior, and identify the person who handles messages in Lead Manager. Avoid placing customer contact details in the migration worksheet.

Record the linked Google Business Profile name, storefront address when applicable, primary category, standard hours, phone, website, and active managers. Save the current verification status and badge. Keep the original image files used in LSA and a dated inventory of photos and callouts.

Google says the campaign receives core business details from the linked Business Profile through one-way sync. Phone, hours, and some minor edits can appear within about 24 hours. A significant business-name change, storefront-address change, or primary-category change may trigger a review that lasts 24 to 48 hours. Make a required accuracy correction, then record it with the date and owner.

Google is deprecating the Better Business Bureau callout during this migration. It recommends other eligible structured callouts and describes a six-callout allowance per category in the migrated experience. Preserve the current wording and evidence so the team can review assets without inventing claims.

Write down who owns each system: LSA administrator, Google Ads administrator, Business Profile manager, manager-account user, report archive, call routing, message replies, CRM export, Day 1 review, and Day 14 comparison. Verify access from each person's own authorized account. Shared passwords create an avoidable handoff risk.

Place the archive in company-controlled storage with the access and retention rules already used for customer records. Separate the performance report from files that contain contact details or call recordings. The campaign migration does not change the business's privacy or retention responsibilities.

Agencies and multi-location operators should keep one row per Customer ID and location. Add notice date, migration date, storefront status, seasonal risk, access risk, archive status, and reviewer. Sort the tracker by migration date and unresolved ownership.

On Day 1, open Campaigns and confirm the specialized pay-per-lead campaign is present and Enabled. Open Campaigns, then Settings, to compare the daily average budget, campaign Target CPA, service areas, schedule, and selected services with the saved record. Open Goals, Conversions, and Leads to confirm Lead Manager access, lead history, messages, and routing.

Review the Business Profile-synced name, address, standard hours, and phone in their own pass. Open Assets to review photos and callouts. Record each difference in a migration fingerprint with the pre-migration value, found value, match status, source, owner, evidence, and resolution.

Correct a documented access, transfer, routing, or verification problem first. Google advises allowing up to two weeks for migration and performance to stabilize. Keep optional budget, bidding, area, and service expansion decisions in a later change window so the record remains interpretable.

Use equal-length pre- and post-migration windows. Compare charged leads, cost, and cost per charged lead in Google Ads with qualified leads, bookings, completed jobs, and revenue from the same business systems used in the baseline. Match weekdays, season, service mix, and operating capacity where the records permit.

Add a separate note for changes made during the comparison window. A budget increase, broader area, new after-hours schedule, staffing loss, price change, or heat wave can affect the result. Keep the date, editor, field, old value, new value, and reason.

Use the Day 14 review as a directional check. It can identify missing settings, routing failures, access problems, or a lead-mix change during the opening period. It cannot provide a universal HVAC benchmark or prove that migration caused each performance difference.

Source review completed July 29, 2026. Rollout timing, transferred settings, report loss, budget conversion, campaign-level bidding, Business Profile sync, Lead Manager location, and stabilization guidance come from Google's LSA migration announcement. Existing report fields come from Google's Local Services Ads report guide. Lead-handling details come from Google's Local Services lead-management guide.

The service-line worksheet, capacity record, ownership map, weighted target examples, and comparison process are PrimeLSA operating recommendations. The dollar figures in the bidding table are illustrative and do not represent a Google formula or an HVAC benchmark.