This guide walks you through migrating from Stape.io to DataNostro in a single afternoon. No tracking downtime, no cookie-keeper data loss, no late-night firefighting.
Why migrate
DataNostro is a Czech-region managed sGTM host with EU-only servers (Frankfurt), CZK invoicing with VAT, and Czech-language support. If you're paying Stape in USD today, you typically save 30–50 % just on currency conversion + transaction fees.
The bigger differentiator: native Sklik & Heureka connectors. On Stape these require a custom HTTP request template. Here it's a checkbox.
Timeline
- Day 0: Prep — DNS access, GTM access, Stape config export (15–30 min)
- Day 1, phase 1: Spin up DataNostro in parallel (60 min)
- Day 1, phase 2: DNS cutover — A/CNAME to DataNostro (5 min + propagation)
- Day 2: Verify, decommission Stape, stop billing
Total: ~3–4 hours of active work spread over 2 days due to DNS TTL.
Pre-flight checklist
- Owner-level access to your Stape dashboard (for config export)
- Access to your Google Tag Manager sGTM workspace
- DNS control of the tracking subdomain (e.g.,
track.yourshop.com) - List of active destinations — GA4, Meta, Google Ads, Sklik, Heureka, TikTok, …
- Meta CAPI and Google Ads Conversion API tokens — copied 1:1
- (Optional) List of Stape Power-Ups in use → look up DataNostro equivalents
Step 1 — Sign up
Register at datanostro.com/signup, pick a plan based on monthly request volume. If you're on Stape Business ($95/mo), the equivalent is DataNostro BUSINESS (1,990 CZK/mo, ~$85) — same limits, same features.
Step 2 — Configure tracking domain
Dashboard → Domains → Add domain. Enter the same hostname you use on Stape (e.g. track.yourshop.com) — but don't point DNS to DataNostro yet! We do DNS at the very end.
DataNostro generates:
- A record or CNAME target (write it down)
- SSL cert auto-issued by Let's Encrypt after DNS cutover
Step 3 — Import GTM workspace
In GTM (sGTM container, not web GTM): Admin → Export Container, download the JSON. Then DataNostro dashboard → Containers → Import GTM, upload the JSON. DataNostro will:
- Spin up a Docker container with your GTM config baked in
- Generate a preview URL for Tag Assistant
- Run a health check on all triggers
Step 4 — Copy platform API tokens
Under Platforms, walk through every destination and copy tokens from Stape:
| Platform | What to copy | Where on Stape |
|---|---|---|
| GA4 | Measurement ID + API Secret | Stape destinations → GA4 |
| Meta CAPI | Pixel ID + Access Token | Stape destinations → Facebook |
| Google Ads | Customer ID + Conversion Action ID | Stape destinations → Google Ads |
| TikTok | Pixel Code + Access Token | Stape destinations → TikTok |
| Sklik | Account ID + API Token | Custom HTTP request template |
For Sklik and Heureka: dramatically simpler here. Instead of a custom HTTP request, just paste Account ID + Token; DataNostro formats and signs the request natively.
Step 5 — Test event via preview URL
Containers → Send test event. A synthetic purchase event fires and you see:
- Per-platform response code (200 ✓ / 400 ✗)
- Latency to each destination
- Exact payload being sent
Stape never gives you this view in one place. Fix any failures before flipping DNS.
Step 6 — DNS cutover
Now update the A/CNAME record at your DNS provider (Cloudflare, GoDaddy, etc.) to point at the DataNostro target. Recommended: drop TTL to 300s a couple hours ahead, switch, then restore TTL to 3600s once stable.
Verify:
dig track.yourshop.com +short
# should return DataNostro IP, not Stape
Step 7 — 24-hour verification
Watch Stats + Activity. After 24 hours, compare to Stape's last-day request count — should match within ±5 % (the gap is usually SSL re-handshake during DNS propagation).
Step 8 — Decommission Stape
Once you have 48 hours of clean data, cancel the Stape subscription. Stape keeps the container alive for ~7 days as a safety net, then auto-deletes.
Plan B — Rollback
If anything goes sideways: revert the DNS A/CNAME to Stape (TTL 300s = 5 min downtime). Don't set DataNostro as primary in any external integrations until you have 48 h of clean data.
FAQ
What about my Stape Cookie Keeper?
DataNostro ships its own Cookie Keeper Power-Up — same job (back up _ga and _fbp to localStorage). One-click activation under Power-Ups.
Will I lose historical data?
No. Historical data lives in destinations (GA4, Meta, etc.), not in the sGTM host. sGTM is forward-only. Post-migration, data continues to flow into the same destinations, so charts in GA4 and Meta stay continuous.
What about custom GTM templates from the Stape marketplace?
Stape templates are standard GTM templates and work on any sGTM host. Leave them in the GTM export — DataNostro runs them unchanged.
Can I get migration help?
Yes. Onboarding is included on BUSINESS plan and above — email [email protected] to schedule a call.