A digital marketing handover checklist helps a business change agencies or bring work in-house while keeping campaigns, reporting and enquiries under control. The difficult part is often the missing context: which account pays for ads, who can publish website changes, which conversion represents a useful lead, and where form notifications arrive. Sending a collection of passwords does not answer those questions. A useful handover combines an asset inventory, appropriate platform access, operating notes and a short acceptance test. This guide explains how a service business can prepare that package, agree responsibilities and check continuity before removing the outgoing team's access. The same approach works for a local Istanbul business and for an international team working across Turkey, the United States or the Gulf, provided the plan reflects its actual working hours and customer journey.
Start with an inventory that names the business owner
Create one register of the assets used to attract, measure and follow up with customers. Include the domain registrar, DNS provider, website hosting, source-code repository, content system, Google Ads account, analytics property, tag container, Search Console property, business profile and relevant social accounts. Record the exact account or property identifier, the business contact responsible for it, the current supplier and the method used to request access. A document saying only 'Google login' is insufficient when several businesses or properties sit under one person's account.
Separate ownership from operational access. Your business should know how an authorised internal person can manage each essential asset independently of a contractor. An agency may operate campaigns through a manager account, but that arrangement needs to be documented alongside the client's own access and billing responsibilities. If an asset is genuinely owned by a third party, flag it before promising a transfer. Discuss the available options and the contractual responsibilities with the relevant owner rather than assuming that a password or exported file settles ownership.
For example, a service company might discover that its website domain belongs to the founder's account while its analytics property was created by an earlier contractor. Put these in separate rows with separate actions. Confirm who can verify the domain, who administers analytics and whether a replacement team can inspect the correct property. Keep recovery arrangements in an approved internal system. The handover register should record that recovery is controlled, without exposing backup codes, credentials or private customer records to everyone reading the project brief.
Invite named users with access that matches the work
Use the platform's own invitation and permission system wherever it is available. Ask each incoming team member to provide the account identity used for work, then have an authorised business administrator approve the required role. A person preparing a report may need different rights from someone changing campaigns or publishing tracking tags. Write the task beside the requested permission so the business can understand why access is needed. Review temporary permissions after the initial assessment instead of treating every invitation as permanent administrator access.
Google Ads documents invitations, changes to access levels and removal of users through its Access and security area. Google Analytics distinguishes roles such as Viewer, Marketer, Editor and Administrator, with account-level roles potentially inherited by properties. Google Tag Manager separates account access from container rights, including editing and publishing. These are separate systems: successfully opening an ads account does not establish access to analytics, and editing a tag workspace does not necessarily permit publication. Check the current official instructions for each asset before choosing a role.
For Search Console, the business should understand who is a verified owner and how ownership is proved. A full user is different from an owner. Google's documentation also explains that verification tokens matter when removing a verified owner. Do not casually remove a DNS record, verification file or website tag during a supplier change. Confirm the business retains verified ownership, document the agreed permission changes, and have the authorised owner perform them. Keep a second appropriate internal administrator where the platform and your operating arrangements support it, especially for essential tag management.
Review measurement responsibilities before granting access →
Transfer the reasons behind campaigns and measurement
Account access is only one part of a marketing handover. Ask the outgoing team for a concise operating note covering active campaigns, intended audiences, exclusions, approved creative, landing pages, budget authority and recent changes. Include scheduled work and experiments that are still running. Identify the person who can approve new claims or service descriptions. An incoming agency should be able to explain what it is inheriting before making changes; otherwise the first week can become an expensive attempt to rediscover decisions already made.
Give measurement its own section. Define what each enquiry event means, how duplicates are handled, whether sales qualification is recorded, and which reports use which attribution or date settings. Note consent behaviour and any known gaps. Preserve a dated baseline export with its filters, time zone and currency so later comparisons have context. A fall in reported conversions after a handover may reflect a changed event, consent setting or reporting window. It is not automatically evidence that campaigns became worse, and a rise is not automatically a commercial improvement.
Keep exports proportionate to the work. A campaign summary, naming guide and anonymised example may be enough for planning without copying an entire customer database. If customer information genuinely needs to move, use your approved process and assign responsibility for the transfer. Document where reusable creative files, approved images and licence records are stored. Keep editable originals when the contract permits it. For campaign links, provide a naming register and live destinations so the incoming team can maintain useful UTM conventions rather than adding a second naming system.
Use a consistent campaign-link register →
Agree a change window and test the customer journey
Choose a handover window that fits the business's enquiry coverage and campaign activity. Name an internal decision maker, an incoming lead and an outgoing contact. Agree which changes are permitted during the window and which require separate approval. Keep routine operations stable while access is being verified; changing hosting, forms, tracking and advertising strategy simultaneously makes a problem harder to locate. If an urgent change is necessary, record its purpose, the person responsible, the expected effect and a practical way to restore the previous working state.
Test a small set of real journeys from the customer's perspective. Open an advertised landing page on a phone, follow the primary contact action, and submit a clearly labelled test enquiry when appropriate. Confirm that the expected recipient receives it and that the customer sees useful feedback. Check links to phone, messaging and booking routes if the business actually uses them. Then compare the relevant measurement signal with the agreed definition. Receiving an invitation is not an acceptance test: the incoming team must be able to perform the authorised work on the correct assets.
For international service teams, record the operating time zone and the hours during which a person monitors enquiries. An Istanbul office and an overseas client may review the same campaign on different calendar days. Keep the shared handover date and reporting period explicit. Check who receives alerts outside normal hours and whether automated acknowledgements accurately describe the next step. Avoid changing customer-facing availability merely to make the handover easier; the published contact information should continue to reflect the business's real service arrangements.
Close the handover with evidence and a review date
Create a short acceptance record for each essential asset: correct identifier confirmed, incoming access tested, internal ownership retained, operating notes received and next action assigned. Record any exceptions with an owner and a target date. Keep unresolved issues visible instead of marking the whole project complete because the new supplier can log in somewhere. A useful closing note might say that campaign review is ready while one archived creative licence still needs clarification. That is more actionable than a broad 'all accounts transferred' statement.
Only after the business has checked continuity should its authorised administrator remove or reduce outgoing access according to the agreed plan. Review direct users, manager relationships, linked tools and other relevant access paths; removing one user entry may not cover every relationship. Do not delete historical campaign data or working configurations as a substitute for removing access. Retain the material the business is entitled to keep and record what changed. If an account cannot be transferred or access is disputed, use the platform's documented support process and the appropriate business contacts.
Schedule a follow-up review after the incoming team has completed a normal operating cycle. Check enquiry delivery, reporting definitions, remaining temporary permissions and whether scheduled work was carried forward. The purpose is to confirm that the handover supports ongoing marketing, not to claim instant ranking or lead improvements. Lead Magneters can discuss your website, campaign priorities and measurement questions as part of a focused consultation. Bring the inventory and the decisions that need attention so the conversation produces clear responsibilities and a workable next step.