Google LSA 14-Day Migration Email: What to Do First

The Google LSA 14-day migration email is an account-specific scheduling notice. Google's LSA migration announcement says the administrator listed on the profile receives the advance email 14 days before migration, a banner appears in the existing dashboard, and Google sends a final reminder seven days later. On migration day, the old dashboard redirects to Google Ads.

You are not being asked to rebuild the campaign by hand. Google says it will transfer the campaign setup, including targeted locations, service types, business categories, budget limits, ad schedule, and business photos. The urgent task is preserving the old performance record because those campaign reports do not move into Google Ads.

Record the migration date in the account time zone, assign one owner, and create the Day 1 and Day 14 review appointments now. A date saved in a calendar without a named owner is not a migration plan.

Start inside the account. Google's public page confirms the notification pattern, but it does not publish one universal sender address for every advertiser. A legitimate workflow can be verified from the signed-in LSA dashboard banner and the account's listed administrator.

If the administrator belongs to a former employee, agency, or franchise contact, treat access as the first migration risk. Identify an active Admin user, document who can change campaign settings, and verify who controls the connected Google Business Profile. Google Ads access-level documentation shows that Read-only users can view campaigns and performance reports, while Standard or Admin access is needed to edit campaigns and Admin access is needed to manage account access.

First, open the current Reports view and save the periods you will need for comparison. Capture a recent operating window, the preceding equal-length window, and a year-over-year or seasonal window when the business has reliable history. Use the account and date range in the filename. Then open the saved file to prove it is readable.

Second, record the current setup: weekly budget, bid mode, any vertical-level targets, selected business categories and services, service areas, ad schedule, call destination, message ownership, photos, and callouts. Google intends to transfer much of this setup. Your record turns a transfer claim into something you can verify.

Third, verify Google Ads, Google Business Profile, and manager-account access. Name the person who will review the new campaign on Day 1. Agencies should add the Customer ID, location, notice date, migration date, export owner, export status, and reviewer to one client tracker.

Use days 2 through 7 to turn screenshots and exports into an operating baseline. Google reports charged leads, spend, lead type, Direct Business Search or Category, and credits. Your CRM or booking system should supply qualified leads, booked jobs, completed jobs, and revenue. Keep the two source systems separate so a platform conversion is not mistaken for a completed job.

Document the call and message handoff. Confirm the phone destination, who answers after hours, who owns message replies, where booked status is recorded, and which users need Lead Manager. The migration does not fix a missed-call or ownership problem.

Multi-service businesses should preserve every current service-level target and the economics behind it. Google is removing vertical-level Target CPA in favor of a unified campaign-level target unless categories are separated into campaigns. Saving the old targets now preserves the context needed for that later structure decision.

When the seven-day reminder arrives, stop collecting new categories of evidence and test what you already saved. Open the report files on another authorized device or ask an authorized second person to locate them. Confirm the files include the account, time period, and metric labels needed for a later comparison.

Recheck the listed administrator, Google Ads access, Business Profile access, and the Day 1 owner. Keep the business name, address, and primary category stable unless a real-world correction is required. Google says significant name, storefront address, or primary-category changes can trigger a verification review and a temporary pause.

Prepare a short Day 1 sheet with the expected campaign, business categories, service areas, schedule, phone destination, daily budget, and Target CPA. The goal is to compare expected and found values before anyone starts optimizing.

The migration affects three different records. Historical campaign performance reports stay in the old dashboard and must be saved. Past customer lead history moves into Google Ads Lead Manager. New campaign performance begins in Google Ads. Treating those records as one data set leads to false deletion claims and broken comparisons.

Google also says verification status and the Google Verified badge carry over. Targeted locations, service types, business categories, budget limits, ad schedule, and photos are intended to transfer. Record them anyway because transfer verification is different from disaster recovery.

PrimeLSA recommendation: avoid combining the platform migration with a rebrand, address move, primary-category change, service-area overhaul, and several budget or bidding edits. Each extra change makes the post-migration record harder to interpret. Complete any correction required for legal or customer accuracy, then document it with a date and owner.

Avoid deleting the local archive after uploading it to a shared folder. Test access first. Keep customer contact details and call recordings in approved storage with the access and retention rules your business already follows. The migration deadline is not permission to move personal data into a public worksheet.

Google tells advertisers to review the migrated campaign inside Google Ads. The initial campaign view should focus on Conversions, Cost, and Cost per conversion. In this specialized campaign, Google describes Conversions as the charged lead count. Use Campaigns and Settings for the daily budget, bidding target, areas, schedule, and categories. Use Goals, Conversions, and Leads for the Lead Manager table.

Google says many ads may run immediately, while the process and performance can take up to two weeks to stabilize. Use the first days to find access, routing, or transfer errors. Reserve the Day 14 review for a directional comparison with equal periods and business context; it is not a promise that performance will match the old baseline.

For an agency or multi-location operator, the email is useful only when it becomes a portfolio-level control record. Keep one row per Customer ID. Record the notice date, migration date, account time zone, administrator, export owner, archive status, access risk, service-mix risk, Day 1 reviewer, and Day 14 owner.

Sort by migration date and unresolved access risk. A client with a later date but no active administrator may require attention before an account with a complete archive and confirmed access. Never send credentials or customer records through the tracker.

Source review completed July 28, 2026. The timing, automatic transfer, report-access, Lead Manager, budget, bidding, and stabilization statements above come from Google's LSA migration announcement. The report fields come from Google's Local Services Ads report guide. PrimeLSA's owner assignments, archive tests, and review cadence are operational recommendations.

Google can change rollout dates and interface labels. Recheck the signed-in account notice and the source page before relying on this guide for a later migration wave.