diff --git a/solutions/images/apm-central-integrations.svg b/solutions/images/apm-central-integrations.svg
new file mode 100644
index 0000000000..5ca3dcab1d
--- /dev/null
+++ b/solutions/images/apm-central-integrations.svg
@@ -0,0 +1,184 @@
+
diff --git a/solutions/images/apm-edge-integrations.svg b/solutions/images/apm-edge-integrations.svg
new file mode 100644
index 0000000000..172a6dfd42
--- /dev/null
+++ b/solutions/images/apm-edge-integrations.svg
@@ -0,0 +1,167 @@
+
diff --git a/solutions/observability/apps/switch-to-elastic-apm-integration.md b/solutions/observability/apps/switch-to-elastic-apm-integration.md
index 1d284e3cc7..4f9bc89926 100644
--- a/solutions/observability/apps/switch-to-elastic-apm-integration.md
+++ b/solutions/observability/apps/switch-to-elastic-apm-integration.md
@@ -35,371 +35,17 @@ Elastic APM consists of four components: **APM agents**, the **Elastic APM integ
APM agents on edge machines send data to a centrally hosted APM integration:
-
-
-
-
+
+
Or, APM agents and the APM integration live on edge machines and enroll via a centrally hosted {{agent}}:
-
-
-
-
+
+
::::{note}
In order to collect data from RUM and mobile agents, which run in browser and mobile applications, you must run {{agent}} centrally. For other applications, such as backend services, {{agent}} may be co-located on the edge machine.
::::
-
## Limitations [apm-integration-upgrade-limitations]
There are some limitations to be aware of: