A new Google Tag Manager account does not give a website a clean slate. The old snippet may still be installed. If the replacement repeats its tracking, a tidier login can leave the business with a less trustworthy conversion count.
Treat the change as a measurement handover, not an account setup. Recover control where possible. Replace what must be replaced. Then prove that the business can manage the implementation and that the site sends the intended data.
A team adding advertising tracking for a client reported an excellent tag-quality status and four visible tag names, yet could not inspect the existing setup. That is the trap: evidence that something is present is not an inventory of everything a replacement must preserve.
Fix permission before replacing delivery
The first question is whether the business needs a different implementation or simply the ability to manage the current one. Those are different jobs.
Google separates account-level administration from container permissions . Read, edit, approve and publish access are not interchangeable. Being able to inspect a container, or having access to the site's Analytics property, should not be treated as proof of the necessary GTM control.
Where an existing administrator can help, establish the business's own authorized access first. Verify the account and container permissions required to manage the setup before removing anyone else's access. Google recommends at least two active administrators and management within the organization, using individual accounts rather than a shared login.
This route can preserve a functioning installation without an unnecessary migration. But administrative access and organizational separation are not the same requirement. If the business must leave a developer's shared account, state that explicitly; an additional invitation may not satisfy it.
An export is a copy, not a completed handover
Creating an independent account can be the right decision when access cannot be recovered or separation is required. The mistake is assuming that an exported file completes the move.
Google's export-and-import process copies container configuration from a chosen version or workspace. Check which version you have. An old export and today's live implementation are not necessarily equivalent.
Review the import's detailed changes before confirming it. Overwrite replaces the destination's existing tags, triggers and variables; Merge has its own conflict choices. A partial export can also leave dependencies missing. Do not treat these options as interchangeable buttons.
Then inspect the resources behind the configuration. Which business controls the destination accounts? Do constants, integrations or other dependencies still rely on the former developer? Have the authorized technical owner check those dependencies securely rather than circulating credentials in a handover document.
The visible GTM container identifier and the advertising conversion identifiers inside its configuration serve different purposes. Preserving the required destination identifiers is a sensible migration goal. It is not a guarantee that triggers, consent behavior or the actual events will remain correct.
Retire the old path deliberately
Before a replacement goes live, map where the old snippet is installed and what else sends the same measurement. Give the developer an explicit replacement plan rather than asking for another tag to be added.
Google warns that repeated configuration of the same Google tag can produce duplicate data or mixed settings . That does not mean every site with two GTM containers necessarily duplicates every event. The risk depends on overlapping configuration and firing behavior, which is precisely why it needs inspection.
Keep a recoverable record of the previous authorized setup. Test the replacement against the journeys that matter: a lead submission, a purchase or whichever outcome the advertising account is meant to count. Check the destination as well as the browser. A tag firing once in a debugging view is a useful check, not the entire acceptance test.
Do not change the measurement definitions and replace the container in the same unexplained step. Keeping a readable before-and-after baseline makes a handover easier to diagnose.
Define what finished means
If the administrator is merely unknown, investigate authorized access rather than assuming the account has no administrator. If nobody has read access, the recovery options are different from a case where a valid export exists. Google's permissions guidance does not offer support as a way around in-product access controls.
No outside account of a migration can guarantee the same outcome on your site. Define completion in terms the business can check: its staff can administer the setup, the intended events reach the right destinations without unintended duplicates, and the old delivery path is accounted for.
The new login is the easiest part to demonstrate. The handover is finished when control and measurement both survive it.