Keep account ownership clear during a marketing handoff

Inventory assets before changing access

List the domain, website hosting, content system, business email, Google Business Profile, analytics, Search Console, advertising accounts, booking tools, and any other active service. For each, record the account identifier, business owner, provider access, billing contact, recovery route, and the person responsible for maintenance.

Our fictional example is a small fitness studio moving to a new website provider. Its domain is held in one account, class bookings run elsewhere, and the old developer receives form notifications. Listing those dependencies first reveals that changing the website alone would leave important operational questions unresolved. Keep passwords and recovery codes out of the shared inventory.

Use the platform roles that match the work

Google Business Profile supports owners and managers, and each person can use their own Google Account. Search Console also distinguishes owners from users with different permissions. Follow the official role documentation when assigning access instead of sharing a single identity among everyone involved.

Our recommendation is to keep the business owner able to administer each core account and give providers the access required by the agreed scope. Some tasks need additional rights; document the reason and review the access after the task. Confirm invitations have been accepted and that the correct property or profile is visible. An invitation email alone is not a completed handoff.

Transfer knowledge as well as account access

Ask for a short operating note: how content is edited, where forms deliver, what sends automated messages, where backups live, which services renew, and how support is requested. Request the approved content and original asset locations. Record any custom integrations and the consequences of stopping them.

ICANN provides guidance on domain transfers and renewals. Consult the relevant registrar instructions before changing domain administration, and distinguish an access change from moving the registration or altering website and email settings.

For the fitness studio, the handoff note identifies the class-booking integration and the staff member who checks inquiries. The incoming provider tests the booking journey and an inquiry reply. This verifies the business process, not simply the ability to sign into a dashboard.

Close the transition in an orderly sequence

Agree on a transition date, who handles open issues, and how unfinished work will be reported. Confirm the business and incoming provider have the required access before removing access that is still needed for continuity. Review former-provider permissions after the agreed work is complete.

Use a final sign-off record with three states: verified, pending, and not applicable. A pending transfer should have an owner and a follow-up date. Save a plain-language note of what changed so the business can understand the setup later without reconstructing a long email chain. The goal is continuity and informed control, including the ability to maintain the site or choose a different provider in the future.