TSA Exit Acceleration
Off the seller’s Datadog organization. Watching its own systems from Day One.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Datadog TSA separation is the work of standing up a dedicated Newco Datadog organization, rebuilding the monitors and dashboards and the integrations, repointing the agents across the estate, handing over the historical telemetry, and exiting the seller organization before Newco hosts keep reporting to the seller. The work sits inside the broader carve-out advisory program because Datadog is where the operational telemetry lands. Treated casually, it leaves Newco systems monitored under seller control and Newco blind to its own infrastructure.
Datadog separation starts with an inventory of the seller organization. The buyer needs the agent estate across hosts and containers, the cloud integrations pulling metrics from the providers, the monitors and alerts, the dashboards, the application performance monitoring and log pipelines, the synthetic tests, the role based access, and the products in use across infrastructure, logs, traces, and security. Datadog is where operational telemetry lands, so the inventory maps how every Newco system is being watched.
The seller runs Newco telemetry inside a shared organization, with Newco hosts reporting alongside the rest of the seller estate, often separated only by tags. The clean end state is a dedicated Newco organization, contracted and administered by Newco, with its own monitors, dashboards, integrations, and access controls. A shared seller organization is acceptable only as a bridge during the TSA, because the seller controls ingestion, sees Newco telemetry, and can change Newco monitors.
Target tenancy strategy turns on whether Newco takes a single organization or a multi organization arrangement, and which Datadog products it genuinely needs. A standalone business with one engineering team usually takes a single organization scoped to its real estate. The decision is settled early because it drives the agent repoint and the integration rebuild.
A clean inventory drives the sequence: the organization build, the monitor and dashboard rebuild, the agent move, the integration reconnection, and the cutover. Because the agents and integrations feed every system into the platform, the inventory is also the basis for keeping observability continuous without leaving a window where systems go unwatched.
Datadog is licensed per host with usage based charges for logs, traces, and the other products, often inside a broader seller agreement. That agreement does not transfer in a carve-out. Newco signs a direct subscription sized to its real host count and the products it uses, whether infrastructure monitoring, log management, application performance monitoring, or the security capabilities. The risk is that Newco inherits a product set and a host commitment scaled for the seller estate.
Datadog reads a carve-out as a buyer that must size a new commitment from scratch. Negotiating leverage comes from the host commitment and from a credible alternative observability platform. The buyer scopes the Newco subscription from the measured host count and usage before negotiating, and writes onboarding support into the contract so the organization and monitors are validated before the agents move.
Where the seller continues to monitor Newco systems through a TSA period, the pricing is cost-plus or fixed-fee with a defined exit ramp, and the TSA defines who maintains the Newco monitors, how historical telemetry is returned, and what visibility the seller retains. Observability cannot lapse, so the TSA keeps the seller organization watching Newco systems until the Newco organization is proven.
Implementation, where a partner is engaged, is fixed fee for defined deliverables under disciplined change control. An organization stand up and an agent repoint have a finite scope, contracted against named hosts, monitors, and a product set rather than open ended consulting time. The engagement model is Fixed Fee plus Portfolio Retainer.
The Newco organization is built and the configuration is rebuilt. The monitors and alert conditions, the dashboards, the tags and the service catalog, the log pipelines and processing rules, and the notification routing are recreated so Newco runs its own observability. The buyer reviews the seller configuration, keeps what fits Newco, and prunes the monitors and dashboards that belonged to seller systems rather than copying the organization wholesale. Configuration as code, where the seller used it, makes this rebuild faster and more reliable.
Moving the agents is the core technical step. The Datadog agent reports to the organization named by its API key, so re homing a host to the Newco organization means updating the agent configuration with the Newco key. Where a configuration management tool deploys the agent, the change is pushed centrally, and where the agent is configured locally each host is updated. Cloud integrations that pull metrics are repointed by reconnecting them to the Newco organization.
The agents are moved in waves so observability never drops. The buyer confirms a host is reporting to the Newco organization before it stops reporting to the seller, avoiding a window where a system goes unwatched. Production hosts and customer facing services are handled with extra care because losing their telemetry during an incident is the costliest gap.
Because the agent runs quietly on the host, the move can be driven centrally where configuration management allows, which makes the agent repoint less user dependent than a desktop migration but no less important to track to completion across the whole estate.
The integration estate is rebuilt around the Newco organization. Datadog pulls metrics from the cloud providers, feeds alerts into the ticketing and incident process, connects to the notification and orchestration tooling, and ties into the deployment pipeline. Each integration is reconnected to the Newco organization so alerts reach the Newco team rather than the seller. A monitor notification left pointing at the seller organization sends Newco incidents to the wrong place.
Historical telemetry is handed over deliberately. The seller organization holds the metrics, traces, and logs for Newco systems, and the buyer decides what Newco needs for continuity, capacity planning, and compliance versus what stays under the seller retention. The history that establishes the performance baseline and satisfies obligations is exported through the API or retained reports so Newco does not lose the record that makes anomalies visible.
The operations handoff is the human side. The seller team watched Newco dashboards and fielded its alerts, and that watch must transfer cleanly to the Newco team or a Newco managed service with no blind spot in between. Where the log pipeline also carries security relevant data, the buyer aligns the handoff with the broader Splunk separation discipline so the continuity of monitoring holds across both platforms.
Identity for the organization is reconnected to the Newco identity provider so Newco engineers authenticate to the Newco organization through Newco single sign on, and seller engineers lose access to Newco telemetry at the right moment.
Cutover moves telemetry from the seller organization to the Newco organization, host by host, with coverage maintained throughout. Because observability cannot lapse, the cutover is sequenced so every system reports to one organization or the other at all times, and the runbook covers the monitor and dashboard activation, the agent repoint waves, the integration reconnection, the operations handoff, and the historical telemetry export.
Validation confirms the platform works on real systems. A repointed agent reports to the Newco organization, the monitors evaluate correctly, the dashboards populate, and a test alert flows into the Newco ticketing and incident process. The buyer validates the telemetry and alert pipeline before scaling the agent move, because an organization that does not surface a real signal is not yet watching the estate.
Stabilization runs while the estate completes the move. Agents that failed to re home, monitors that misfire, and broken integrations are triaged within agreed service-level commitments and treated with priority because a gap in observability is an operational exposure. The buyer tracks the share of hosts reporting to the Newco organization before certifying the platform for TSA exit.
Decommissioning the seller observability is explicit. Once Newco hosts report to the Newco organization and the TSA tail closes, the seller stops ingesting Newco telemetry, confirms the seller team no longer sees Newco data, and the agreed historical telemetry has been returned to Newco.
Datadog separation cost is driven by the per host subscription and the usage based charges, and by the effort of repointing agents and rebuilding the monitors and integrations. The discipline is to size the commitment to Newco real host count and usage, choose the products Newco genuinely needs rather than the full seller suite, and control log and custom metric volume, which is where Datadog spend escalates when it goes unmanaged.
The common failure mode is creating a coverage gap during the move. A host that stops reporting to the seller before the Newco organization is watching it goes dark, and the missing window is exactly the one an incident will fall into. Buyers that sequence the agent move so every host always reports somewhere avoid the gap.
The common operational mistake is neglecting the historical telemetry and the operations handoff. An organization with no history loses the baseline that makes a spike meaningful, and dashboards no one watches are not monitoring. The fix is to transfer the agreed history and hand off the watch cleanly. A PMO maintains the dependency map across the organization, identity, and the integration stack, escalating blocks inside forty eight hours.
A clean Datadog separation produces a Newco that monitors its own systems in its own organization, with its own monitors and its history intact, and a seller that no longer sees Newco telemetry. The discipline runs through the TSA exit acceleration program under a Fixed Fee plus Portfolio Retainer engagement model.
Yes. The clean end state is a dedicated Newco Datadog organization, contracted and administered by Newco, with its own monitors, dashboards, integrations, and access controls. A shared seller organization is acceptable only as a bridge during the TSA, because the seller otherwise controls ingestion, sees Newco telemetry, and can change Newco monitors and alerts.
The Datadog agent reports to the organization identified by its API key, so re homing a host means updating the agent configuration with the Newco organization key. Where a configuration management tool deploys the agent, the change is pushed centrally, and where the agent is configured locally each host is updated. Cloud integrations that pull data are repointed by reconnecting them to the Newco organization.
The seller organization holds the historical metrics, traces, and logs for Newco systems. The buyer decides what Newco needs for continuity, capacity planning, and compliance, and that history is exported through the API or retained reports before exit, while the seller keeps only what its own obligations require. Newco preserves the baseline that makes anomalies visible.
By sequencing the agent move so every host keeps reporting to one organization at all times. The buyer confirms a host is sending to the Newco organization before it stops sending to the seller, so no system goes unmonitored. A gap in observability is most costly during an incident, so the move is planned to prevent one.
Deployment strategy, the forwarder repoint, and the operations handoff for Newco.
Read the article →Console strategy, the agent redeployment, and the security operations handoff.
Read the article →Organization strategy, the repository move, and the CI handoff for Newco engineering.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →Scope the data split tightly. Every table you over-migrate and every pipeline you leave on the seller is a line on next year's TSA invoice.