Transfer primary ownership without locking out the new owner

Make the handover an access transaction

A business sale or internal succession does not automatically change the account controlling its profile. Before the handover, list the public profile link, current primary owner, intended incoming owner, and other authorized users. Agree which business continues to operate; a completely new identity may require a different profile decision.

Keep the profile transfer separate from domain ownership, advertising accounts, booking software, and customer records. Those systems can be related, but access to one does not prove access to the others. A short handover table prevents someone from believing that a website login also transfers the Maps listing.

Check both accounts before choosing a date

Have the incoming owner confirm the exact Google Account they will retain after the transfer. Ask them to accept the invitation and show that the expected profile appears in their account. Do not use a temporary employee account or an email that will disappear when the old company stops operating.

Google limits certain actions for new owners and managers during their first seven days, including primary-ownership changes. Put the accepted-invitation date in the handover record so the transfer is not scheduled on an assumption. Leave enough operational overlap to correct an invitation sent to the wrong account.

Perform and verify the transfer

• Have an existing owner invite the incoming person through People and access.
• Confirm the invitation is accepted and the incoming account sees the correct business.
• Check whether the seven-day new-user restriction applies before attempting the ownership change.
• Have the current primary owner assign Primary owner to the intended user and save the change.
• Check the resulting roles from both sides before the departing user stops managing the profile.

Keep old access only for a defined purpose

Decide whether the outgoing owner needs any temporary role to finish a specific handover task. If so, set a review date and a named task rather than leaving unrestricted access indefinitely. Remove access when the authorized role ends, using the appropriate owner account.

Do not delete the old Google Account first and hope the profile follows the buyer. Do not hand over a password as a substitute for role management. The seller's account may contain unrelated personal information, and a shared login leaves no clear boundary between old and new management.

Test the business information after the handoff

Once the role change is confirmed, check phone, website, hours, action links, pending updates, and notification delivery. Make necessary factual corrections with an edit log. If the business's identity is also changing, review Google's rebranding criteria separately rather than assuming all historical information automatically belongs to the new operation.

The transfer is complete when the new owner has the intended control, the outgoing person's access matches their remaining authority, and customer paths work. Record those outcomes; do not use rankings or review totals as a substitute for a verified ownership handover.

Worked example

For example, Cedar Shoe Repair continues operating under the same name after a sale. The buyer accepts an owner invitation on October 2. The seller does not attempt to make the buyer primary owner that afternoon; the handover schedule accounts for Google's new-user limitation. After the role change is possible and saved, both check People and access. The buyer then tests the existing phone and website before removing the seller's unnecessary access. This is a planning example, not a promise that every sale meets Google's rebranding rules.

Questions about this task