Skip to content
DATANOSTRO ACADEMY

Migrating from Stape to DataNostro step by step

What needs reconnecting, how to verify nothing's missing, and how to do the cutover without lost conversions. A realistic 3-5 day plan.

10 min Read Středně pokročilý Updated 5.6.2026

Migrating from Stape is an hour of work, not three days — if you have a plan. This guide describes a cutover with no downtime window, where your tracking doesn't miss a single day.

Day 0 — scan your existing setup

  • Stape dashboard → container → copy the Container Config (a text field, base64-encoded JSON).
  • Open the Power Ups tab → note which are active (Cookie Keeper, Anonymizer, Custom Loader, etc.).
  • Stape → Domains → note the CNAME target.
  • In the GTM web container, note the measurement ID and transport URL.

Day 1 — parallel setup in DataNostro

  1. Create a DataNostro project (Settings → Fill in billing details → Free trial).
  2. In the Containers tab, paste the same Container Config. The tags import 1:1.
  3. In the Domains tab, add tracking.yourstore.cz.dn as a subdomain (default) — it'll run in parallel with the Stape domain.
  4. In Power-Ups, enable the same set of extensions (the name mapping Stape → DataNostro is 1:1).
  5. In Platforms, fill in the credentials for each platform (GA4, Meta CAPI, Google Ads, …). The tokens are the same, you just copy them into the new UI.

Day 2 — parallel test

Send the same test event to both platforms (Stape + DataNostro) and compare that they send the same payloads. Use Meta Test Events or GA4 DebugView.

  • If the cookies don't match (e.g. _fbp generated on different subdomains), activate Cookie Keeper in DataNostro.
  • If the _ga client_id is missing, check that Custom Loader is on with the same datalayer_var as on Stape.

Day 3 — DNS cutover

In Cloudflare (or your DNS provider), change the CNAME for tracking.yourstore.cz from the Stape target to the DataNostro target. Set TTL = 60s a few hours before the cutover so the cache doesn't flicker.

After the DNS update, watch the Real-time event log in the DataNostro dashboard. You should see events from real visitors' browsers within 5 minutes.

Days 4-7 — parallel run + sunset Stape

Leave the Stape container running for another 3-5 days as a safety net (cookies migrate from its domain to the new one). Then cancel Stape billing and DataNostro runs solo.

Security safeguards

  • Don't reuse Stape access tokens in DataNostro — generate new ones. Stape could (in theory) still listen on a compromised key.
  • After the cutover, raise the DNS TTL back to 3600s.
  • After a week, cancel the Stape container entirely — billing keeps running there even after the domain is off.

If you don't want to do the migration yourself, the DataNostro Care Premium package does it for you (5-7 days, fixed price CZK 39,900) including 30 days of hyper-care after the cutover.

Did this article help you?
✓ Thank you for the feedback