# Migration path/plan from Heartbeat uptime to Synthetics App does not exist

**URL:** <https://discuss.elastic.co/t/migration-path-plan-from-heartbeat-uptime-to-synthetics-app-does-not-exist/370628>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [November 15, 2024, 10:15pm UTC](https://discuss.elastic.co/t/migration-path-plan-from-heartbeat-uptime-to-synthetics-app-does-not-exist/370628 "2024-11-15T22:15:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![FaizanGit](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/faizangit/32/139009_2.png) [@FaizanGit](https://discuss.elastic.co/u/FaizanGit)\
**Post date:** [November 15, 2024, 10:15pm UTC](https://discuss.elastic.co/t/migration-path-plan-from-heartbeat-uptime-to-synthetics-app-does-not-exist/370628/1 "2024-11-15T22:15:18Z")

</div>

Is there a migration path/plan for customers who are currently using Heartbeat Uptime App, and have to start using Synthetic App due to deprecation announcement from Elasticsearch? I am referring to [Uptime monitoring deprecated in 8.15.0](https://www.elastic.co/guide/en/observability/8.15/uptime-intro.html).  
I was able to find how to migrate uptime rules to synthetics rules at the link [here](https://www.elastic.co/guide/en/observability/current/monitor-status-alert.html#migrate-monitor-rule).  
I was hoping to find a roadmap/transition plan by Elastic to migrate off from Heartbeat uptime to Synthetics. Some information that would highlight what changes customers will experience, what impacts it will have to the alarms/dashboard etc. Merely mentioning to use Synthetic App is not much of a help. Is there a migration/transition plan?