# Migrating to Discovery

Discovery changes the way Caplin Platform deployments are licensed; how components connect to each other; and how data services scale. You can take advantages of these improvements in steps or in full.

## Converting an existing deployment

You can convert an existing deployment to Discovery in steps. Take advantage of Discovery’s features at your own pace.

| # | Step | Description |
| --- | --- | --- |
| 1 | [Deploy Discovery server](discovery-deploying-discovery.md) |  |
| 2 | [Connect DataSources to Discovery](discovery-connecting-datasources-to-discovery.md) | Monitor your deployment in Discovery’s [web interface](discovery-web.md) and gain automatic Transformer clustering. |
| 3 | [Migrate to Discovery licensing](discovery-licensing.md) | Benefit from a simpler licensing model and the freedom to deploy licensed DataSourcesfootnote:[The following Caplin Platform products require a licence: Liberator, Transformer, and the TREP Adapter] to any IP address. |
| 4 | [Migrate to peer discovery](discovery-migrating-peer-discovery.md) | Simplify DataSource connectivity configuration. |
| 5 | [Migrate to scalable data services](discovery-migrating-scalable-data-services.md) | Add new DataSource instances to your deployment without downtime for data-service reconfiguration. |

## New deployments

If you are designing a new deployment, or you are migrating an existing deployment to a new deployment architecture, such as Kubernetes, then we recommend that you take advantage of all Discovery’s features from the outset.