Crest Data joined the engagement mid-stream, inheriting alert conversions that another contractor team had already completed and marked as validated. Working with a single dedicated engineer and Dynatrace’s native migration tooling, Crest Data delivered the full scope in four weeks. Along the way, we reviewed the process, identified and corrected logic gaps in the inherited alerts before they reached production, turning a high-risk handoff into a clean, on-time delivery and restoring the customer’s confidence in the migration.

About the Customer  

The customer is a global management consulting firm that advises leading organizations across industries and geographies. With a large, distributed workforce and a technology estate that supports critical client-facing and internal operations, the firm relies on reliable, real-time observability to maintain service performance and resolve incidents quickly. As part of a broader observability modernization initiative, the firm chose to consolidate its monitoring on Dynatrace and connect its alerting directly to its ServiceNow IT service management workflows.

Customer Challenge  

The firm needed to move a substantial volume of Splunk assets, approximately 100 dashboard panels and 400 alerts, to Dynatrace, with ServiceNow integration for those alerts included in the scope.

Before Crest Data was engaged, a separate contractor team had converted and validated the alert logic. Crest was brought in specifically to implement that work and integrate it with ServiceNow, not to repeat the conversion. Because the alerts arrived pre-converted and were represented as validated, their actual quality only became visible once implementation and customer review sessions were underway.

Proposed Solution & Architecture

• Alert implementation at pace: Crest Data Implemented ~400 pre-converted alerts into the live Dynatrace environment.
• Dashboard migration: Delivered ~100 panels using Dynatrace’s own migration tooling.
• ServiceNow integration: Delivered ServiceNow integration for the migrated alerts within the same migration window, extending the engagement beyond a pure lift-and-shift into a functioning, connected alerting workflow.
• Rapid turnaround: Completed the engagement in 4 calendar weeks (20 working days) with a single engineer – a materially faster timeline than this volume of migration and integration work would typically take. 
• Quality assurance and remediation: During customer review sessions, the team identified and corrected issues in the inherited alert conversions that would otherwise have shipped with defects – protecting the customer from alerts that looked complete but would not have functioned as expected.

De-Risking a Mid-Project Handoff

Crest Data did not start this migration from the beginning. It inherited the project partway through, building on another team’s work, and that handoff is where much of Crest’s value emerged.

1. Stepping into a live, in-flight project: Crest Data joined after the project had already started, taking on alert logic from another contractor team that had been represented as fully validated – a common but high-risk situation, since the incoming team has no visibility into how that “validated” work was actually produced.
2. Verifying the hand-off instead of just trusting it: Rather than treating “already validated” as final, Crest’s review process during customer sessions surfaced real gaps – missing conditions and incorrect logic – that would have affected how alerts behaved in production. Catching this before go-live is exactly the kind of safety net a mid-project handoff needs.
3. Standardizing inconsistent work: Much of the inherited alert set showed signs of manual, one-off creation rather than a consistent process, which had introduced inconsistencies and a higher likelihood of conversion errors. Crest’s implementation pass helped surface and correct these rather than propagating them into production.
4. Raising the bar to platform best practice: Where migrated alerts didn’t consistently follow Dynatrace best practices, Crest gave the customer the opportunity to address them during implementation rather than inheriting them later as a maintenance burden.
5. Rebuilding confidence through visible remediation: Quality issues surfaced during validation had, at points, reduced the customer’s confidence in the migration. Crest’s structured review, correction, and revalidation of the inherited alerts rebuilt that confidence and brought the engagement to a successful close.

Outcomes & Success Metrics

Crest Data delivered the Splunk-to-Dynatrace migration and ServiceNow integration in just four weeks, with a single engineer, while remediating inherited alert defects before go-live.

• ~400 alerts implemented in the customer’s Dynatrace environment
• ~100 dashboard panels migrated using Dynatrace’s native migration tooling
• 4 weeks (20 working days) to complete the full engagement
• 1 dedicated engineer delivering the entire scope
• ServiceNow integration delivered for all migrated alerts within the same window
• Zero known inherited alert defects carried into production, with logic gaps caught and corrected during customer review

Key Takeaways

• Speed under constraint: A single engineer delivered ~100 panels, ~400 alerts, and ServiceNow integration in 4 weeks – compressing a migration and integration effort that could otherwise have run considerably longer.
• Splunk-to-Dynatrace migration delivered with quality built in: Crest moved approximately 100 Splunk dashboard panels and 400 alerts to Dynatrace, standardizing inconsistently built alerts and aligning them with Dynatrace best practices along the way. The customer received a cleaner, more maintainable monitoring estate, not just a like-for-like copy of what it had in Splunk. 
• Turned a risky handoff into a clean delivery: Even though the alerts arrived “pre-validated” from another team, Crest’s review process caught real logic gaps before they reached production, protecting the customer’s monitoring reliability.
• Expanded scope, same window: ServiceNow integration for the migrated alerts was delivered within the same timeframe as the core migration, not as a separate follow-on effort.
• Tooling flexibility: The engagement was delivered using Dynatrace’s own native migration tooling rather than Crest’s proprietary tool – demonstrating Crest can execute effectively within a customer’s or platform vendor’s preferred toolchain, not only its own.

Conclusion

Observability migrations rarely fail because of volume alone. They fail when inherited work goes unquestioned and defects quietly make their way into production. In this engagement, Crest Data stepped into an in-flight Splunk-to-Dynatrace migration, delivered the full scope of dashboards, alerts, and ServiceNow integration in just four weeks, and applied the scrutiny needed to ensure every alert worked as intended.

The result was more than a completed migration. The customer gained a standardized, best-practice-aligned alerting estate connected directly to its ITSM workflows, along with renewed confidence in its observability platform. For organizations navigating complex platform transitions, particularly those inheriting work mid-project, this engagement shows how the right partner can accelerate delivery while reducing risk.

About Crest Data

Crest Data is a data and AI-driven technology solutions provider for enterprises and technology innovators in cybersecurity and observability, backed by 1,000+ professionals and 5,500+ successful projects across 175+ global customers. Crest Data partners with leading platforms including Dynatrace, ServiceNow, Datadog, AWS, Google, and Grafana. Crest Data helps organizations modernize their observability ecosystems through fast, low-risk platform migrations and integrations that connect monitoring directly to IT service management workflows.