Migrating to Other Platforms

Last updated: August 6, 2026

Planning a migration? Let us know

As soon as a migration is on your roadmap, reach out to your Noibu CSM — the earlier the better, as it gives us time to prepare and support you through the transition. Sharing your plans early means we can keep your monitoring running smoothly with no gaps in coverage.

When you're ready, please fill out the form below with the details of your planned migration. It captures everything we need, including your new domain URLs, any changes to your site design or checkout flow, new payment gateways, updated success URLs, and whether you'd like your existing data wiped.

Fill out this form: Migration Form

Deployment options

See here on how to deploy via: Google Tag Manager — Add a Custom HTML tag containing the Noibu script and set the trigger to All Pages.

See here on how to deploy: Manual — Add the script directly into your page's HTML <head>.

Important: Once your new deployment is live, remember to remove any previous Noibu deployment method. Running two at once can cause duplicate data and conflicts in your monitoring.

Why head placement matters

Noibu needs to load as one of the very first things on the page so it can catch errors as they happen in the <body>. When the script loads from within the body instead, you risk incomplete monitoring — the SDK may not work as expected, it can conflict with other scripts, and other error loggers may capture errors before Noibu ever sees them.