# Migrate from ServiceInsight to ServicePulse


ServiceInsight has been sunset and will receive no further updates. It will be deprecated on February 10, 2027, at which time it will no longer be supported. 

ServicePulse is the recommended replacement for visualization and debugging capabilities. 

## Migrating

### Prerequisites

- A running instance of [ServiceControl](/servicecontrol/index.md) is required, and any system already using ServiceInsight meets this prerequisite. This is because both ServiceInsight and ServicePulse read the same message data directly from ServiceControl with no requirement for data migration.
- ServicePulse hosted using any of the following ways:
  - Integrated ServicePulse (ServiceControl 6.13 or later). [Integrated ServicePulse](/servicecontrol/servicecontrol-instances/integrated-servicepulse.md) runs inside the ServiceControl Error instance and is automatically configured to connect to it, so no separate installation is needed. It is also upgraded automatically whenever ServiceControl is upgraded.
  - Docker for running ServicePulse in a container. This is best suited for cross-platform environments or monitoring multiple systems. 
  - A Windows machine with .NET Framework 4.5 or later to install ServicePulse directly. Only one instance can be installed at a time, so if there are multiple systems to monitor then multiple distinct [URL connection configurations will need to be used](/servicepulse/host-config.md#configuring-connections-via-servicepulse-url-query-string-parameters).
- A currently supported version of Microsoft Edge, Chrome, Firefox, or Safari.

### Migration steps

1. Open ServiceInsight and take note of the connection urls.
  ![ServiceInsight connection urls](images/si-migration-si-connections.png 'width=400')

2. Get ServicePulse running and configured with the connection URL [using containers](/servicepulse/containerization/index.md) (recommended) or by [installing to a Windows machine](/servicepulse/installation.md).

    Each method provides a way to configure the URL during setup, but it can also be configured in the ServicePulse UI afterwards:

    ![ServicePulse connection settings](images/si-migration-sp-connections.png 'width=800')

    If [monitoring](/servicepulse/how-to-configure-endpoints-for-monitoring.md) is enabled on your endpoints system, the ServiceControl monitoring url can be configured at this time to allow ServicePulse to display monitoring information.

 3. Optionally, uninstall ServiceInsight. It will continue to function as long as the ServiceControl api remains the same, but it will no longer receive updates and support will end when it is deprecated.

## Known limitations

### Connection to multiple ServiceControl instances

ServicePulse currently connects to one ServiceControl instance at a time. If multiple ServiceControl URLs were previously configured in ServiceInsight, use a separate ServicePulse container for each system that needs to be monitored, or bookmark [separate URLs](/servicepulse/host-config.md#configuring-connections-via-servicepulse-url-query-string-parameters) for each primary and monitoring connection configuration.

### Custom message viewer plugins

There is currently no equivalent to the [custom message viewer plugin model](/serviceinsight/custom-message-viewers.md) used by ServiceInsight; however, a [feature request has been created](https://github.com/Particular/ServicePulse/issues/2778) so leave a comment if you need that functionality.