Apple Business Connect Migration: A Multi-Location Audit

Apple Business Connect is no longer the current name of Apple's business-listing product.

On April 14, 2026, Apple replaced Business Connect, Business Manager, and Business Essentials with Apple Business. Apple said existing Business Connect locations, place cards, photos, organization information, and account details would migrate automatically.

For a multi-location service brand, migration is the easy part. The real work is deciding which branches belong in Apple Maps, which facts should inherit from the brand, which actions need a location-specific destination, and who is allowed to change each record after an acquisition, opening, or closure.

What migrated automatically, and what still needs review

Use Apple Business as a governed location system, not a one-time directory submission. Confirm that the migrated organization and locations are correct. Keep one canonical record for every real customer-facing branch. Let brand identity cascade where it should, but keep hours, coordinates, phone routes, actions, photos, and status local.

Apple says a place card can appear in Maps, Siri, Calendar, Messages, and Spotlight. That makes a wrong branch record a customer-experience problem even if Google drives more leads today.

After the cleanup, run a location-level visibility check for the markets and services that matter. The audit should distinguish Apple record accuracy from whether a separate AI product actually cites or recommends the brand.

Apple Business combines location marketing with device management, business email, calendars, directories, and support in one platform. This guide covers the location and brand surfaces, not the device-management rollout.

The product name changed, but three operating objects still matter.

A brand carries identity such as the name, logo, categories, and cover image. A location represents one physical business place associated with a brand. A place card is the customer-facing record that can carry the location's hours, photos, actions, and other details across Apple.

That separation matters after a rollup. The parent organization can govern a brand without turning every branch into the same record. A 70-location HVAC platform may use one approved logo and visual identity, while keeping different hours, phone routes, booking URLs, categories, and entrances for Phoenix, Tucson, and Las Vegas.

Apple also says organizations can manage each location separately whether they have one location or 1,000. A bulk footprint does not excuse branch-level QA.

Decide which records belong in Apple Maps

Apple's current guide describes place cards as extensions of physical locations. The add-location flow asks the operator to enter an address, place the marker over the correct building, and use satellite or hybrid view to locate the entrance.

That is a useful eligibility guardrail for service brands. A staffed med spa, hotel, restoration office that receives customers, or garage-door showroom may have a clear physical location to manage. A plumber's private home, a virtual office, a mailbox, or a dispatch territory should not be presented as a public storefront merely to gain another map record.

If a service-area operation has no qualifying customer-facing place, do not invent one or expose a private address. Maintain the Apple brand features available to the organization, keep owned location and service pages accurate, and ask Apple Business Support about the exact operation before adding a location.

This is also where duplicate records surface. Search Apple Maps before creating anything. If the location already exists and another organization manages it, Apple's flow lets the verified business request a transfer and attach supporting documentation. Apple says that review can take up to five business days.

The same identity discipline applies outside Apple. Use the citation cleanup guide to compare the branch with Google, Bing, relevant directories, and owned pages before creating another public version of the business.

Build one canonical record per eligible branch

An Apple location needs more than a name and street address. The branch record should resolve the display name, physical address, precise entrance, primary category, opening status, opening date when relevant, phone number, website destination, regular hours, special hours, and internal location code.

The location code is not displayed to customers, but it gives the portfolio a stable join key. Use the same code in the source-of-truth location table, website CMS, call-routing system, review program, analytics, and partner exports. A branch renamed after an acquisition should not lose its internal identity because the public display name changed.

For a 45-location pest-control platform, the canonical record should make it possible to answer a simple question without opening five systems: Which branch owns this address, which phone route reaches it, which website page represents it, when can customers visit, and who approves a change?

Coordinates deserve an explicit check. Apple tells operators to move the marker over the correct building and makes entrance placement part of the location flow. A geocode at the middle of a shopping center or industrial park can send a customer to the wrong door even when the street address is technically correct.

When a new branch is preparing to open, Apple allows an Opening Soon status with an opening date no more than six months away. Coordinate that date with the new-location launch workflow so the Apple record, location page, phone path, and operating readiness describe the same branch.

Let brand identity cascade without flattening local facts

Apple associates every location with a brand and lets some brand details cascade to locations. Shared identity is useful for logos, a canonical brand name, and approved visual assets, but it should not erase local truth.

A hospitality group may want one brand cover image across 30 properties, then choose location-specific photos for a resort entrance, airport hotel, and downtown conference property. An HVAC rollup may use one parent brand identity while preserving branch-specific hours, emergency coverage, phones, actions, and categories.

Set a simple ownership rule. Corporate marketing owns brand identity and reusable creative. Regional operations owns hours, status, and customer-entry facts. The digital team owns URLs, analytics parameters, and partner access. A named location manager confirms the live customer experience.

When the public brand changes, do not update Apple in isolation. Reconcile the website, profiles, citations, call greeting, vehicle identity, and review response name with the rebrand source-migration workflow.

Make every location Action finish a real customer job

Apple Actions add direct links to a brand website or preferred platform from a place card. Available action types depend on category. Apple uses examples such as ordering, tickets, reservations, waitlists, pickup, and delivery.

For service operators, an Action succeeds only when its destination completes the branch-level handoff.

A hotel reservation action should land on the correct property and preserve dates when the booking system supports it. A med spa appointment action should not route every market into a generic treatment form that cannot show provider or location availability. A service brand's website action should reach a page that identifies the branch, service area, phone route, and next step.

Apple permits common UTM parameters on Action URLs, including utm_source, utm_medium, utm_campaign, utm_term, and utm_content. Apple prohibits GCLID parameters, login trackers, single sign-on parameters, and tokens in those URLs.

Use a consistent source value such as Apple Maps, then preserve the branch identifier in an approved campaign or content parameter. Test the destination on a mobile device, complete the call or booking path, and confirm the lead arrives with enough branch context for operations to act.

Apple requires approval before an Action appears, and its current guide says approval can take up to three business days. Put action review in the launch timeline instead of adding it on opening morning.

Control roles, partner access, and acquisition transfers

Apple Business supports internal roles and third-party delegation. Apple says a verified organization can share selected brands and location features with an approved third-party partner through OAuth or a Partner Organization ID.

That is safer than sharing an administrator's password. It also creates a clean boundary for a franchise marketing partner, listing vendor, or acquisition integration team.

Delegate the smallest useful scope. A partner that updates photos, hours, and Actions for one brand does not need access to every current and future brand. Record the partner organization, delegated features, covered brands, internal owner, approval date, and planned access review.

Apple notes that partner-managed content remains subject to the same policies as content the organization creates. Delegation moves the work, not accountability.

Acquisitions need two separate controls. First, transfer management of an existing location when the seller or former agency still owns it. Second, decide whether the location should keep its current brand or move to the parent brand. Apple says changing a location's associated brand deletes its showcases and retains its insights; the category, logo, or cover photo may also change with the brand. Record those effects before the move. Do not solve an ownership problem by creating a duplicate.

Offboarding matters too. Remove former agencies and integration partners after the handoff, then verify that internal administrators can still update the locations. A quarterly access review is cheap compared with discovering during a holiday-hours incident that the only capable account belongs to a former vendor.

Treat Apple-suggested changes as location incidents

Customers can report incorrect place-card information. Apple says it may edit a location's name, status, or hours after reviewing reports, then email users who can manage the location.

Those changes should enter the same incident queue as a profile suspension, bad call route, or closed-location error. Review whether Apple's correction matches the real branch. Accept it when it is right. Contest it with current supporting information when it is wrong.

Do not let these notices disappear into a shared inbox. Assign an owner, record the affected location code and field, compare the canonical source, and read back the public place card after the decision.

Closures need the same care. In Apple's removal flow, choosing "someone else manages this location" removes the location from the account. Choosing "permanently closed" also marks it closed in Maps. Use the closed-location cleanup workflow to reconcile status, ownership, redirects, profiles, and public citations.

Read Apple reports without overclaiming

Apple's multi-location reports cover searches, place-card views, and Actions. They can be viewed by day, week, month, or total period, and downloaded as CSV.

The reports are available for brands with 2,000 or fewer locations and include up to 14 months of history. Apple allows up to five reports to run at once, with one brand per report.

There is an important privacy caveat. Apple represents usage below a reporting threshold as zero. A zero can therefore mean activity was below the threshold, not necessarily that nobody searched, viewed, called, or booked. Apple recommends longer aggregation periods for low-volume data.

For operators, the useful scorecard is location-aware. Compare search taps, place-card views, action taps, and the downstream calls or bookings the destination can attribute. Separate mature locations from new ones, physical customer-facing branches from other operating models, and brand searches from category searches.

Do not convert an Action tap into booked revenue without downstream proof. Do not compare Apple metrics with Google Business Profile metrics as though the products use identical definitions. Read each platform's documented event, then connect it to the accepted lead, appointment, or sale in the system that owns that outcome.

Where Apple Business fits in the source stack

Apple Business gives a brand direct control over an important Apple-facing record. It does not replace the website, Google Business Profile, Bing Places, review platforms, industry directories, or the operating systems that hold current branch facts.

The practical model is one canonical location record with several public destinations. Correct the source of truth first. Publish the change to Apple and other relevant platforms. Read back what customers can see. Then test which sources appear for real Google and AI queries using the cross-engine source guide.

That order keeps claims honest. Apple says its place cards appear across Apple products. It does not say a complete Apple record causes ChatGPT or Google AI Search to recommend a business. If another product cites Apple Maps for a specific prompt, capture that result. If it cites the location page, Yelp, an industry directory, or another source, fix the source that actually appeared.

Run the rollout in four control passes

Organization control: audit the migrated organization. Confirm verified status, active users, partner access, brands, location count, duplicate candidates, unmanaged locations, and missing source-of-truth location codes. Sample at least one mature branch, one acquisition, one opening, and one edge case.

Location truth: reconcile every eligible physical location against the canonical record. Fix the marker, entrance, category, hours, status, phone, website, and brand association. Escalate duplicates and ownership transfers instead of creating replacements.

Customer handoff: update place-card assets and Actions. Use brand-level defaults only where they remain true locally. Add approved tracking parameters, test each destination on mobile, and confirm the branch receives enough context to complete the customer handoff.

Measurement and maintenance: download a baseline location report, document Apple's reporting thresholds, and connect visible Actions to downstream outcomes. Add Apple-suggested changes, access reviews, openings, rebrands, and closures to the recurring location-operations queue.

Close the rollout when customers can find the right physical branch, see current information, complete a working next step, and the organization can name the owner of every field.

Sources

• Apple Newsroom: Introducing Apple Business. Launch date, retired products, and automatic Business Connect migration.
• Apple Business User Guide: Intro to Apple Business. Apple Business scope and the brand, location, and place-card model.
• Apple Business User Guide: Add a location. Physical location setup, entrance placement, transfer requests, and opening-soon rules.
• Apple Business User Guide: Edit or remove a location. Location fields and the two removal outcomes.
• Apple Business User Guide: Maintain location information accuracy. Customer-suggested changes, Apple review, and manager notifications.
• Apple Business User Guide: Share access with a third-party partner. Partner Organization IDs, OAuth, and delegated brand features.
• Apple Business User Guide: About Actions. Category-dependent Actions, primary Actions, and approval timing.
• Apple Business User Guide: Action URL standards and guidelines. Allowed analytics parameters and prohibited URL data.
• Apple Business User Guide: Update a location's brand. Showcase deletion, insight retention, and possible category or creative changes.
• Apple Business User Guide: Location reports for multiple locations. Report limits, intervals, history, and privacy-threshold behavior.

Amadeus Peterson is the CTO & Co-Founder of Cheers, the local search platform for multi-location service businesses.