Apache Kafka®️ 비용 절감 방법 및 최적의 비용 설계 안내 웨비나 | 자세히 알아보려면 지금 등록하세요
Migrate your data and infrastructure from any Kafka source: topics and data, schemas, connectors, access control, and clients. Our tooling moves clients incrementally, so applications keep running with minimal coordination and downtime.
The hard part of a migration is coordination, not replication. Confluent makes it easy: your clients connect to a gateway, Cluster Linking replicates in the background, and a single command flips a whole batch of topics to Confluent when you're ready.
You watch replication lag and pick the moment. Nothing switches until you run the command.
Every client is repointed once to a single Confluent Gateway address. From then on, the gateway swaps their authentication and routes them to Confluent underneath, with no further restarts or config changes.
Migrate a single topic or a group. Cluster Linking replicates byte-for-byte with offsets preserved, so consumers resume where they left off.
Traffic is held until every byte is replicated and lag hits zero, then the topic is promoted. Each move is reversible until cutover completes.
Confluent's migration tool, KCP, works with any Kafka cluster. It scans your source environment, assesses the move, and migrates every resource onto Confluent Cloud.
Clients connect to a single gateway endpoint that never changes. As each topic
is promoted, the gateway starts routing it to Confluent while the rest keep
flowing to the source — no client changes, no downtime.
You don't move topics and leave the rest behind. KCP migrates the whole estate. Each layer is handled by a specialized Confluent component, coordinated for you.
| Resource | Handled by | What happens |
|---|---|---|
| Topics & data | Cluster Linking | Copied byte-for-byte, with consumer positions preserved so applications resume where they left off. |
| Schemas | Schema migration | Moved into Confluent Schema Registry before any data moves, so your schemas are in place when applications arrive. |
| Connectors | Connect Migration Utility | Supported connectors re-created as Confluent managed connectors, along with their configuration and state. |
| Access control | ACL & identity mapping | Existing users, roles, and ACLs mapped to Confluent service accounts and ACLs. |
| Applications | Migration Gateway | Repointed once and cut over with no code changes, and their re-authentication handled for them. |
| Cost baseline | Assessment | Your current spend pulled from your real usage, so you have a baseline to compare against before you move. |
Replication, verification, and cutover, step by step.
Discover and migrate your connectors to Confluent Cloud.
Plan your migration Answer a few questions about your environment and get a sequenced migration.
Assess your environment Run a scan of your current cluster to see every resource and what it costs you today.
Talk it through Walk your specific setup through with a Confluent migration specialist.