Switch

Switch from your current monitoring, on-call or ITSM tool.

Keep what you run today while MeerStack proves itself on real traffic. Cut over when the numbers match, and not before.

The approach

Move over without a migration weekend.

Three phases. Your current tool stays on until you turn it off.

  1. 01

    Assess

    Run the importer in dry-run mode against your current setup or an export file. You get a report of what imports cleanly and what needs attention, and nothing is written.

  2. 02

    Run in parallel

    Send the same telemetry to both. MeerStack monitors can notify through supported paging tools, so you compare alerts and dashboards on real incidents for as long as you need.

  3. 03

    Cut over

    Move paging to MeerStack on-call when you are ready. Re-run the importer at any time: it updates what changed and never duplicates.

What moves today

What the tooling does today.

Built and tested in our codebase. If it is not on this list, it does not move automatically yet.

Keep your agents

Agent-compatible intake: if your hosts run a supported agent, point it at MeerStack. Metric series, distributions, check runs, logs and host metadata arrive unchanged. OpenTelemetry (OTLP/HTTP) metrics and logs work too.

Import dashboards, monitors and downtimes

For supported platforms, the migration CLI reads your setup through the platform’s public API, or reads an export file. Composite monitors are rewired to the imported IDs. Monitors with no data yet import as drafts that never notify.

meerstack migrate import --file export.json --dry-run

Re-run safely

Imports are idempotent: a re-run updates what changed and reports unchanged objects. Credentials are never logged or written to the report.

Old links keep working

A migration ID map sends old dashboard and monitor deep links to the imported object, so runbooks and bookmarks do not break.

Integration assets

Dashboards, monitors and log pipelines that ship with open-source agent integrations import with one command.

meerstack migrate integrations

Page through what you have

During the parallel run, monitors can notify supported paging tools, Microsoft Teams, Slack, email or any webhook.

Not automatic yet

  • Traces and APM data: MeerStack does not ingest traces yet.
  • SLOs, incidents and notebooks are not imported.
  • On-call schedules and escalation policies from other tools, and ITSM records, have no importer yet.
  • There is no built-in side-by-side alert comparison; you compare in your own tools during the parallel run.
Switch guides

Guides for the tool you run today.

What moves, what does not yet, and the public facts we compared against, each with its source and date.

Help moving

Design partners get hands-on help from the founding team.

Tell us what you run today. We will tell you honestly what moves and what does not.