Do I need Actility's involvement to migrate to Datacake?

No. Migration is self-serve: you keep the same DevEUI, JoinEUI/AppEUI and AppKey, so no vendor-coordinated cut-over is needed. The migration is essentially a re-routing of your gateway packet-forwarder and a re-registration of devices on Datacake.

Will my carrier roaming or OSS-PMR integrations still work after the migration?

No. Those are ThingPark-specific telco features and Datacake does not provide them. If your deployment depends on carrier roaming or OSS-PMR, Datacake is not a like-for-like replacement. Most enterprise (non-carrier) deployments do not depend on those features.

What about my custom payload codecs from ThingPark?

Datacake's template catalog covers most popular hardware so you typically do not need to bring your codec at all. For unusual hardware you can paste your existing JS decoder into Datacake's per-device decoder field.

Can I keep my Actility gateways?

Yes. Any LoRaWAN gateway running Semtech UDP Packet Forwarder or LoRa Basics Station works with Datacake. The gateway hardware does not change.

How long does the migration typically take?

For an enterprise deployment of a few hundred to a few thousand devices, a single engineer can complete the migration in a few days, including CSV bulk import, validation and downstream re-pointing. Larger fleets are typically migrated in batches over a week or two.

← Datacake LoRaWAN Network Server

Migration guide

Migrate from Actility ThingPark to Datacake's free LoRaWAN Network Server

A practical, no-firmware-re-flash migration path from Actility ThingPark to Datacake's managed LNS. Run both stacks in parallel during the cut-over so you never lose a device, then decommission the old server when you're ready.

Re-use the same DevEUI, JoinEUI/AppEUI and AppKey: no firmware re-flash
Cut over gateway-by-gateway with zero downtime
400+ device templates ready, with payload decoders included
Free LNS in every Datacake plan, no per-gateway fees

Create a free Datacake account Jump to the steps

Actility ThingPark vs Datacake at a glance

A side-by-side view of the parts of the LoRaWAN stack that change when you migrate. We've kept it factual. Both products have their strengths.

Capability	Actility ThingPark	Datacake
Pricing model	PartialQuotation-based, tiered by gateway / device / region count	Public per-device pricing; LNS and gateways free
Per-gateway pricing		Gateways are free at every plan tier
Built-in dashboards	PartialThingPark X application / dashboard tier (separate product)	Template-driven dashboards on the same account
Built-in rules / alerting	PartialAvailable in ThingPark X application tier	Email, SMS, push and webhook actions with escalation
MQTT / Webhook outputs
Re-use existing devices (no re-flash)
Self-serve migration	PartialVendor-coordinated; depends on contract scope	Self-serve: keys re-used, no vendor coordination required

Capabilities reflect the public product documentation of Actility ThingPark and Datacake at the time of writing. ThingPark's product family includes several tiers (Wireless, Enterprise, Community, OSS-PMR), so please cross-check on actility.com for the specific edition you operate.

Migration in 5 steps

A self-serve path from ThingPark to Datacake. Re-use existing keys, bring existing gateways, run both stacks in parallel during the cut-over.

1
Create a free Datacake account
Sign up at app.datacake.de. Datacake's LoRaWAN Network Server is included on every plan, with no commercial commitment required to validate the migration.
Pro-tip:Use a domain-matching email so any internal IT change-control later finds the right account ownership.
2
Re-route your gateway packet-forwarder
Datacake works with the same gateway hardware classes you operate on ThingPark: RAK, Kerlink, Multitech, Tektelic, Cisco IXM, etc. Configure the gateway's packet-forwarder (Semtech UDP or LoRa Basics Station) to point at Datacake's LNS endpoint. For zero-downtime cut-over, migrate gateway-by-gateway in maintenance windows.
Compatibility:Datacake terminates Semtech UDP and LoRa Basics Station, with no carrier-grade or telco-specific protocols required.
3
Re-register your devices
Add devices to Datacake using the same DevEUI, JoinEUI/AppEUI and AppKey from ThingPark. Where the hardware is in our template catalog, applying the template configures the payload decoder, dashboard and downlink hooks automatically.
Bulk migration:Export device identifiers and keys from ThingPark into a CSV, then bulk-import into Datacake. Avoid manual re-typing for fleets larger than a handful of devices.
4
Verify uplinks and downlinks
Watch the Datacake device list for joins and uplinks. For Class C / Class B devices, exercise a downlink to confirm the round-trip works end-to-end. Decoded values should match what you see in ThingPark X.
Sanity check:Compare last-uplink timestamps against ThingPark for 5-10 minutes per device class. When they match, the device is on Datacake.
5
Cut over and align downstream consumers
Once devices are stable on Datacake, decommission the ThingPark device entries and re-point your downstream consumers (MQTT subscribers, webhooks, ETL) to the Datacake equivalents. ThingPark webhooks and Datacake webhooks both carry decoded JSON, so most mapping changes are just field renames.
Rollback:No firmware was changed. To roll back, re-point the gateway at ThingPark and re-activate the existing ThingPark registrations.

Still evaluating?

Compare Actility ThingPark vs Datacake side by side

Pricing, hosting model, integrations and where each platform wins, laid out in a single comparison table.

Read the Actility ThingPark comparison

Actility ThingPark migration FAQ

Ready to get started?

Create your free account and start monitoring temperature, humidity and air quality in minutes, or book a demo to see how Datacake fits your use case.

Get Started Free Book a Demo

Get in touch

We typically reply within one business day.