What Breaks When a MarTech Stack Moves From Agency to In-House

A mid-size e-commerce client decided to bring their MarTech stack in-house after three years of an agency running GTM, their email platform, and most of their reporting. The tools transferred fine — admin access, billing, configuration, all of it moved over in about a week with minimal drama. What broke was everything that lived in the agency's heads rather than in the tools.

The undocumented decisions that surfaced

The agency had three custom GTM variables with names like "checkout_flag_v2" with no documentation on what they were for or why "v2" existed. There was a segmentation logic in the email platform that excluded a specific customer cohort from a win-back flow, with no record of why — it turned out to be a fix for a complaint from eighteen months earlier that the in-house team had no memory of.

An agency relationship accumulates institutional knowledge the same way code accumulates technical debt, and neither shows up in an invitation to a shared dashboard.

What actually fixed it

• A systematic audit of every active automation and tag, documenting purpose even when it meant guessing and flagging the guess clearly.
• Interviewing the departing agency team before the contract ended, not after — the knowledge window closes fast once the relationship ends.
• Treating anything undocumented as a candidate for deletion rather than assuming it was load-bearing, then watching closely for breakage after removal.
• Building a lightweight internal wiki from day one, explicitly to avoid recreating the same opacity in-house.

The in-house team eventually got the stack to a healthier, better-documented state than the agency had left it in, but it took almost three months of archaeology to get there. If you're planning this kind of transition, budget time for the handoff interviews as seriously as you budget for the technical access transfer — the technical part is the easy part.