Migration to Elastic: from Splunk, Datadog and other platforms
We move monitoring, logs and alerts from Splunk Cloud, Datadog and other platforms to Elastic Stack. We start with an audit of your current environment and finish with recreated dashboards and alerts in Kibana. The old platform keeps running until the new one has taken over. Where Grafana fits better, we migrate to that too.
Why companies change platform
-
Costs grow with data volume
The price depends on data volume, and the volume keeps rising. We compare the cost of your current platform with the alternatives before we start the migration.
-
The platform no longer meets new requirements
You need other features, an open solution or more control over your data. We choose a target platform to suit those requirements.
-
Years of accumulated clutter
Hundreds of dashboards and alerts, half of them unused. A migration lets you carry over only what is needed and tidy up the rest.
-
Fear of a gap in monitoring
Switching off the old platform without a replacement is a risk. We run the new one alongside the old and switch over when everything works.
Migrating a monitoring platform is more than moving data. You also have to recreate what your team works with: dashboards, alerts, queries and integrations. That is why we start with an audit and a list of what is really used.
We most often propose Elastic Stack and, as an Elastic partner, supply licences and implement the platform. If you choose Grafana, we build it the same way as for new infrastructure monitoring.
How we price
We set the price after the audit. It depends on the volume of historical data, the number of dashboards, alerts and integrations, the source and target platforms, and how long they must run in parallel.
What we do
- We audit your current environment: data sources, volumes, dashboards, alerts, queries and integrations
- We help choose the target platform: most often Elastic Stack, and also Grafana with Prometheus and Loki
- We prepare a migration plan with a schedule, resources and risks
- We move historical data, clean it and adapt it to the new format
- We configure and implement the target platform
- We recreate dashboards, reports and alerts on the new platform
- We migrate to Elastic Stack from Splunk Cloud, Datadog and other platforms, and also from Datadog to Grafana
- We hand knowledge over to your team and maintain the new platform on request
Who it is for
- You use Splunk Cloud and are looking for a cheaper or more open platform, such as Elastic Stack
- You use Datadog and want to move to Elastic Stack or to Grafana with Prometheus and Loki
- You run several monitoring tools and want to replace them with one
- You want to change platform but cannot afford a gap in monitoring
From Splunk Cloud to Elastic
We analyse your Splunk environment: data volumes, queries, dashboards and integrations. Then we plan the move to Elastic Stack and recreate in Kibana what is in use.
- Audit of the environment and requirements
- Export and transformation of historical data
- Recreation of dashboards, reports and alerts
From Datadog to Elastic
We audit your Datadog configuration: metrics, dashboards, monitors, alerts, logs and traces. We move them to Elastic Observability and recreate dashboards and alerts in Kibana.
- Mapping metrics, logs and traces to Elastic Agent and OpenTelemetry
- Rebuilding dashboards and alerts in Kibana
- A migration plan with a schedule and risks
From Datadog to Grafana
Where Grafana fits better, we audit your Datadog configuration, design a Grafana architecture with sources such as Prometheus and Loki, and recreate what you need.
- Mapping metrics to the format of the new sources
- Rebuilding dashboards and alerts in Grafana
- Choice of data sources, for example Prometheus and Loki
How we work
- 1
Audit
We list the data, dashboards, alerts, queries and integrations and check what is actually used.
- 2
Platform choice
We compare target platforms for features, cost and maintenance.
- 3
Migration
We move the data and recreate dashboards and alerts. The new platform runs in parallel with the old one.
- 4
Switchover
We check the results with your team, switch over and decommission the old platform.
Experience
- We work on Elastic Stack, Grafana, Prometheus, Grafana Loki, OpenTelemetry, Datadog and Splunk, so we know the platforms on both sides of a migration.
Frequently asked questions
Will monitoring go dark during the migration?
It does not have to. We start the new platform alongside the old one, compare results and only then switch over. That way there is no gap in visibility.
Will you move our historical data?
Yes, if you need it. We agree with you how far back and in what form, because a full transfer can be costly and some data no longer has value.
Will you recreate our dashboards and alerts?
Yes. We recreate the ones your team actually uses and help tidy up the rest. We agree the exact scope after the audit.
Which platform can you move our monitoring to?
Most often to Elastic Stack: Elasticsearch, Kibana and Elastic Security. Where it fits better, to Grafana with Prometheus and Loki as well. We advise on what suits your environment and budget best.
See also
-
Elastic Stack implementation: licences, deployment and support
Official Elastic partner: licences, implementation, cluster cost and performance optimisation, maintenance and on-call.
-
Log management in Elasticsearch and Kibana
Logs from applications, clouds, networks, virtual machines and hypervisors on one platform: collection, search, retention and alerts.
-
Kibana dashboards: data visualisation, reports and alerts
Kibana dashboards, and Grafana where data comes from other sources: charts, maps, tables, reports and alerts for IT teams and management.
