Quick answer
Verify transfer accuracy before changing strategy
Check five systems after LSA migration: services and locations, budget and Target CPA, schedule and lead routing, Business Profile sync and verification, then assets and supporting controls. Use a before-and-after migration fingerprint and resolve confirmed transfer errors before adding optional changes. Reviewed against Google's migration documentation on July 29, 2026.
What this covers
- Campaign setupCompare services, locations, budget, bidding, and schedule with a dated pre-migration record.
- Customer contactTest call routing, message ownership, Lead Manager access, and Business Profile synchronization.
- Change controlCorrect confirmed transfer errors first and preserve every post-migration edit in Change history.
Five-setting verification system
Verify the migrated account in one controlled pass
Give each field a pre-migration value, a found value, evidence, an owner, and a resolution. Use that migration fingerprint to separate a transfer problem from a later optimization decision.
Reach and economics
Campaigns > Settings: selected service categories, job types, service areas, exclusions, and campaign status.
Availability and routing
Campaigns > Settings and Goals > Conversions > Leads: ad schedule, phone path, messages, and Lead Manager users.
Trust and presentation
Linked Business Profile and Assets: synced identity, verification, photos, callouts, and transfer evidence.
Find the migrated campaign and record its starting state
Open the Google Ads account named in the migration completion notice and confirm its Customer ID. Select Campaigns and locate the specialized Performance Max campaign that uses Local Services pay-per-lead goals. Google says this campaign keeps pay-per-valid-lead billing and Search and Maps placements, even though it now sits inside Google Ads.
Read the campaign status before opening individual settings. Record Enabled, Paused, under review, or another status as shown. Then save the date, time, reviewer, and account time zone. A later team member can use that starting record to distinguish the original transfer condition from a status change.
Use your saved migration inventory for the comparison. The LSA migration checklist covers the nine records worth preserving before the old dashboard closes. Without that record, use dated screenshots, approved reports, manager notes, or account-change evidence and label the confidence of each comparison.
Create a before-and-after migration fingerprint
Use one migration fingerprint for all five settings. Enter the pre-migration value, the value found after migration, whether they match, the source for each value, the person responsible, the evidence file, and the final resolution. Keep this worksheet free of customer contact details.
Use Match for an exact transfer, Expected conversion for a documented interface change such as weekly budget becoming daily, Mismatch for a transferred value that differs, Missing for a control or asset that cannot be found, and Pending review for a Google verification state. Add the date to every status.
Use the fingerprint to keep the sequence legible. The reviewer can show what Google transferred, what the team corrected, and what changed later as an optimization. Agencies can keep one row set per Customer ID and location.
| Field | Pre-migration value | Found value | Status | Source | Owner | Evidence / resolution |
|---|---|---|---|---|---|---|
| Service categories | ____ | ____ | ____ | Inventory | ____ | ____ |
| Service areas | ____ | ____ | ____ | Inventory | ____ | ____ |
| Daily budget | Expected: weekly ÷ 7 | ____ | ____ | Budget record | ____ | ____ |
| Campaign Target CPA | ____ | ____ | ____ | Bid record | ____ | ____ |
| Ad schedule | ____ | ____ | ____ | Schedule record | ____ | ____ |
| Phone and message owners | ____ | ____ | ____ | Routing record | ____ | ____ |
| GBP identity and verification | ____ | ____ | ____ | GBP record | ____ | ____ |
| Photos and callouts | ____ | ____ | ____ | Asset inventory | ____ | ____ |
Setting 1: Services and locations
In Campaigns, open Settings and compare selected services and locations with the saved inventory. Google says it intends to transfer targeted locations, service types, and business categories. Confirm active and inactive selections because an unwanted service can alter lead mix while a missing service can remove relevant demand.
Review service-area targeting in its own pass from the Business Profile address. Google's LSA service-area and job-type guide documents the existing job-type and service-area controls. The migration announcement says service areas remain editable in Google Ads while the storefront address comes from the linked Business Profile.
Correct a missing, extra, or wrong location when the pre-migration record is reliable and the difference affects serving. Record the original found value before editing. Leave expansion ideas for a later decision window.
- Business categories and every active service or job type.
- Included cities, ZIP codes, service areas, and exclusions.
- Campaign status and any review or eligibility message.
- Storefront identity and the intended Customer ID or location.
Setting 2: Daily budget and campaign Target CPA
Open Campaigns > Settings and record the displayed daily average budget. Calculate the expected value from the old weekly average divided by seven. For example, a $1,400 weekly average becomes a $200 daily average. Google describes the monthly spending limit as $200 multiplied by 30.4, or $6,080 in this example.
Keep the daily average and monthly limit in separate columns. The daily figure is an interface and pacing control; multiplying one busy day by 30 does not prove the account will spend that amount. Use the Google Ads cost record for actual spend.
Record the campaign Target CPA beside each prior service-level target. Google is deprecating manual bidding and vertical-level Target CPA. The migrated structure uses one campaign-level target unless the advertiser separates service groups into campaigns. Preserve the old service economics before accepting or changing the new target.
| Check | Expected record | Found in Google Ads | Resolution |
|---|---|---|---|
| Daily average budget | Old weekly average ÷ 7 | ____ | Verify arithmetic before editing |
| Monthly spending limit | Daily average x 30.4 | ____ | Use as the stated account limit |
| Campaign Target CPA | Saved target or documented migration result | ____ | Compare with service economics |
| Prior vertical targets | Preserved by service line | No vertical control | Use in campaign-structure review |
Setting 3: Ad schedule and lead routing
Check the ad schedule in Campaigns > Settings. Compare all-day, business-hours, or custom time blocks with the saved schedule. Google's LSA ad-scheduling guide explains those schedule modes. Verify the Google Ads account time zone because a correct-looking hour in the wrong time zone can shift coverage.
Open Goals > Conversions > Leads and confirm Lead Manager access. Review the lead table, message panel, charged status, and permitted export controls. Google says past customer leads transfer, including contact details, message history, and older call recordings. Google's Local Services lead-management guide provides the existing lead-management context.
Place an approved test through the operating path when possible. Confirm the phone reaches the intended team, messages have a named owner, and after-hours behavior matches the schedule. Record the test time and result without adding personal customer data to the worksheet.
- Ad schedule by weekday, time block, and account time zone.
- Primary phone destination and any approved forwarding path.
- Message ownership, response coverage, and escalation timing.
- Lead Manager access for the people who review, book, or export leads.
- Voicemail, overflow, after-hours, and missed-call handling.
Setting 4: Business Profile sync and verification
Open the linked Google Business Profile and compare business name, storefront address, standard hours, phone, primary category, website, managers, and verification status with the pre-migration record. Then compare the identity shown in the migrated Local Services campaign.
Google describes the connection as a one-way sync from Business Profile to Google Ads. Phone, hours, and some minor business-name updates can appear within about 24 hours. A significant business-name change, storefront-address change, or primary-category change may trigger a review lasting 24 to 48 hours and can pause serving during that review.
Edit a factual business-identity error at its source in Business Profile. Service areas and the ad schedule remain campaign controls in Google Ads. Give a pending sync and a transfer mismatch different statuses so the team does not repeat the same edit in several systems.
Setting 5: Photos, callouts, verification, and supporting controls
Open Assets and compare the migrated photos with the original file inventory. Google says it intends to transfer business photos and allows up to 100 photos in the migrated experience. Confirm that the images belong to the correct business or location and that authorized users can manage them.
Review callouts by service category. Google is deprecating the Better Business Bureau callout. It recommends at least six other structured callouts where eligible and describes a six-callout allowance per category. Keep claims factual and supportable; migration is not a reason to add awards, guarantees, affiliations, or availability claims that the business cannot verify.
Record verification badge status, licenses or insurance status where the interface makes them available, and any account-level notice that affects eligibility. Keep these records as evidence fields. Avoid inferring a private ranking formula from their presence or order.
Use Change history for the new audit trail
After recording the starting state, open Campaigns > Change history. Google Ads Change history documentation explains how to review edits by date, user, campaign, and change type. Use it as the post-migration record for changes made inside Google Ads. It does not restore the old LSA report or prove what a pre-migration setting was.
Export or capture the relevant period after every material correction. Record the field, old value, new value, editor, time, reason, evidence, and planned review date. A support-assisted correction also needs an internal note because the business still needs to understand the final state.
Agencies should restrict edits to named users and use manager-account access rather than shared credentials. Review Change history before a client performance meeting so an account change is not presented as unexplained platform movement.
Decide what to correct now and what to review later
Correct a confirmed material transfer error that affects campaign serving, customer accuracy, access, lead routing, verification, or billing controls. Capture evidence before and after the correction. Make one coherent correction set when several fields belong to the same issue, then assign a review date.
Place optional changes to budget, Target CPA, service areas, service mix, schedule expansion, and asset testing into a later decision window. Google advises allowing up to two weeks for migration and performance to stabilize. The period still needs operational monitoring, but a valid transferred setting does not require an immediate optimization edit.
Escalate through signed-in Google support when a required control is missing, permissions block the responsible user, the campaign belongs to the wrong account, the verification state conflicts with the source profile, or a documented transferred value cannot be corrected. Keep case numbers and resolution dates in the fingerprint.
Use a Day 1, Day 7, and Day 14 review cadence
Review Day 1 for transfer accuracy and access. Review Days 2 through 7 for routing, message ownership, verification, and spend pacing. Use Day 14 for a directional performance comparison with equal periods and the same definitions.
Read Conversions as charged leads in this specialized campaign, then compare Cost and Cost per conversion. Add qualified leads, booked jobs, completed work, and revenue from the business's approved systems. Label every source and time window.
A migration review is complete when the five setting groups have an owner, a status, evidence, and a resolution or planned review date. A campaign that appears to be serving can still have a routing or reporting gap, so completion should cover the operating path as well as campaign status.
Source and operating note
Source review completed July 29, 2026. Campaign location, transferred settings, budget conversion, bidding changes, Business Profile sync, Lead Manager paths, asset limits, and stabilization guidance come from Google's LSA migration announcement. The audit-trail guidance uses Google Ads Change history documentation.
The migration fingerprint, correction sequence, owner fields, and review cadence are PrimeLSA operating recommendations. Google can change interface labels during rollout, so confirm the signed-in account and current source documentation before using a later version of this checklist.
Editorial note
Written by Arthur Z and last updated July 29, 2026. PrimeLSA keeps public guidance practical, Google Local Services Ads-specific, and connected to real account review.