All articles Use case

Retail: is the platform ready to migrate?

A worked architecture review of a made-up retailer's self-managed Confluent Platform before a move to a managed service: what to fix first, what to fix during the move, and what the move itself changes.

November 13, 2026 · 5 min read

Teams often plan a move from self-managed Kafka to a managed service as if the move itself will fix the platform. Some problems do go away (broker tuning, operating-system settings, zone layout); others move with you (topic design, authentication, schemas, monitoring), and a few should be fixed before anything moves. An architecture review in InsightKafka is a way to sort them.

Example. Brindle Lane Retail, its clusters and its findings are made up (the product's sample engagement, renamed). Whether a given setting carries over depends on the target service; check its documentation.

The environment

The fictional retailer runs two Confluent Platform 7.5 clusters on Google Cloud (orders and staging) for order management, inventory and customer analytics, with MySQL change capture and a BigQuery sink. The engagement is an architecture review with four goals: migration readiness, connector architecture, configuration for e-commerce workloads, and monitoring.

An architecture review engagement for a made-up retailer: score 58 marked at risk, Confluent Platform, phase during engagement, the executive summary and engagement goals, and counts of findings by severity.
The engagement overview: a score of 58, at risk, and the goals of the review.

What the review found

Six findings for the made-up retailer: two critical (SASL/PLAIN with no ACLs, insufficient replication on the clickstream topic) and four high (no Schema Registry, a failed BigQuery sink connector, no alerting, a single availability zone).
Six findings: two critical, four high, each with its category and source.
Connectors on the made-up orders cluster: a running MySQL change-capture source with three tasks and a failed BigQuery sink with two.
The connector view makes the failed sink obvious.

Sorting the findings for the move

  • Before the move: anything that loses data or hides problems. A clickstream topic with too few replicas can lose data today; a failed sink connector means data is already missing downstream; no alerting means the migration itself will be flown blind.
  • During the move: anything the target platform does differently. Authentication and ACLs, and schema governance, are set up on the new platform anyway; design them properly there rather than patching the old one.
  • With the move: anything the managed service takes over, such as zone layout and broker tuning. Check that the service tier you choose actually provides it.

Fixing the two critical findings before the move

  • The under-replicated clickstream topic. Raising the replication factor of an existing topic is a partition reassignment (in Apache Kafka, kafka-reassign-partitions with a plan that lists more replicas), not a configuration change. It moves data between brokers, so schedule it and throttle it. If the topic is recreated on the target platform anyway, decide whether the risk until cut-over justifies the work.
  • SASL/PLAIN with no ACLs. Every client can do everything today. Inventory which principals read and write which topics now, from client configuration and team knowledge; that inventory is what the target platform's access model is built from.

Questions to put to the target platform

AreaQuestionWhy it matters for this retailer
AuthenticationWhich mechanisms are supported, and how are service accounts managed?Today's SASL/PLAIN clients will all need new credentials
ConnectorsAre the change-capture source and the BigQuery sink available as managed connectors?Otherwise a Connect cluster still has to be run
SchemasIs a schema registry included, and with which compatibility modes?There is none today; contracts are being written from scratch
ReplicationWhat replication factor and zone layout does the chosen tier enforce?Whether the zone finding goes away with the move
NetworkingPrivate connectivity from the cloud network the producers run in?Order and inventory services must reach the new cluster

Trade-offs in the plan

Fixing everything on the old platform first gives a clean migration but spends effort on a cluster that is being retired. Moving first and fixing after is faster but carries known data-loss risks through the cut-over. The sort above is a middle path: fix what can lose data now, design what the new platform will do differently, and verify what the managed service is supposed to take over.

Running the before-and-after comparison

  1. Keep the current engagement as the baseline: findings, checklist and score.
  2. After cut-over, start a new engagement for the same customer with the same checklist and upload the new platform's configuration and listings.
  3. Run the analysis and compare findings by category with the baseline.
  4. Explain every finding that is new, as well as every one that disappeared.
The report for this engagement type. In the current release the report templates cover two engagement types: the Kafka health check and a production readiness assessment. An architecture review or migration readiness engagement keeps the same tabs, findings and score, but its own report template is not built yet; ask us how we handle the read-out for one.

A read-out for a migration review

A migration audience wants a decision, not a gauge. A structure that works for this kind of engagement:

  1. The score and the two critical findings, in one slide.
  2. The sorted list: before, during, with the move, with an owner for each “before” item.
  3. The questions for the target platform, with who will get the answers.
  4. The date of the post-cut-over health check.

Leave the score for the end of the first slide: for a team about to migrate, the number matters less than whether the “before” list has owners and dates. Keep the six findings and their evidence as the appendix. If someone asks why an item is in “before”, the answer is on the finding.

Questions

Does InsightKafka plan the migration itself?

No. It assesses the current platform and records findings and recommendations; the sort into before, during and with the move is the architect's judgment, shown here as one way to do it.

Will the failed connector show up in the score?

If the analysis drafts a finding for it, yes: a high in connectors costs that category 15 points and the overall score 1.5. Its real weight is in the data already missing downstream, which is why it is in the “before” group regardless.

Can it assess the target platform before cut-over?

Yes, as a separate engagement, if there is a target cluster to describe. A production readiness assessment is the template designed for that point, with go/no-go criteria and readiness sections.

Example · Brindle Lane Retail

A migration plan with a health check at both ends

The fictional retailer's platform lead takes the three “before” items into the current quarter, writes the authentication model and schema contracts into the migration design, and books a second health check in InsightKafka for a month after cut-over, on the new platform, with the same checklist. Comparing the two engagements' findings is the evidence that the migration improved the platform rather than just moving it.

Next: consultancies: one method across every customer.

Run your next health check in InsightKafka

Bring one cluster's broker configuration, its topic and consumer-group listing and the questions your team keeps asking. We set up the engagement and walk through the findings with you.

Request a demo