---
title: "Migration Scenarios"
slug: "kproxy-migration-scenarios"
description: "Choose the right configuration path for flow collection and SNMP enrichment to enhance your observability with Kentik's Universal Agent."
updated: 2026-03-04T23:35:09Z
published: 2026-03-04T23:35:09Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.kentik.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Migration Scenarios

Select the migration path from `kproxy` to [**Universal Agent**](/v1/docs/universal-agents) that matches your observability needs:

### **Scenario 1: Flow Collection Only**

Use this path if you require NetFlow, sFlow, or IPFIX ingestion without immediate SNMP-based enrichment.

1. Install and register the Universal Agent on your host.
2. In the Kentik portal, navigate to **Settings »** **Universal Agents**.
3. Enable the **Flow Proxy** capability for the agent.
4. Configure the local listening port (default 9995) and map the agent to the appropriate Site and My Network settings.
5. In **Settings »** **Networking Devices**, edit the target device(s) to set their SNMP option to **Disable SNMP Collection from this device**.

### Scenario 2: Enriched Flow without Full Monitoring

Use this path for enriched flow collection. SNMP data is used to map traffic data to interface names, descriptions, and speeds but the device will not be monitored by Kentik NMS or have access to related features.

1. Enable the**Flow Proxy** capability as described in [**Scenario 1**](/v1/docs/kproxy-migration-scenarios#scenario-1-flow-collection-only).
2. Enable the **SNMP/ST** capability on the same agent instance.
3. In **Settings »** **Networking Devices**, edit the target device(s) to set their SNMP option to to **Agent-based SNMP for Flow Enrichment**.
4. Configure your SNMP v2c or v3 credentials and specify the desired polling intervals.

### Scenario 3: Enriched Flow and Full Monitoring

> [!NOTE]
> **Note**: This is the **Kentik-recommended** **path** for full visibility and requires a [**DevicePak**](/v1/docs/licenses#devicepak) license. Collected flow traffic data is enriched with interface names, descriptions, and speeds. The device’s performance, health, and operational state are also monitored by NMS.

1. Enable the**Flow Proxy** capability as described in [**Scenario 1**](/v1/docs/kproxy-migration-scenarios#scenario-1-flow-collection-only).
2. Enable the **SNMP/ST** capability on the same agent instance.
3. In **Settings »** **Networking Devices**, edit the target device(s) to set their SNMP option to to **Agent-based SNMP for Flow Enrichment**.
4. Configure your SNMP v2c or v3 credentials and specify the desired polling intervals.