Overview

Zero-downtime migration, owned by our engineers

Eight moves, each built on the method the engine documents, run by OSStend engineers into our cloud, your cloud account or your data center.

45 minutes with an engineer: we review your workload and sketch the design.

  • Operated by AceMQ
  • Engine-documented methods

OSStend migrations use the method each engine documents: federation and shovel for RabbitMQ, logical replication for PostgreSQL, replication for Valkey, mirroring for Kafka, and reindexing or snapshots for OpenSearch. Engineers run the migration and own the cutover, with both sides live until you switch.

160+AceMQ customers
10+Years running these systems
24/7Engineers on call
3Places it runs: our cloud, yours, your data center
Engines we run, on the platforms you already use
  • PostgreSQL
  • MySQL
  • MongoDB
  • Redis
  • Valkey
  • OpenSearch
  • Kafka
  • RabbitMQ
  • AWS
  • Google Cloud
  • Azure
  • Kubernetes
  • OpenShift
  • Prometheus
  • Grafana
  • Datadog
  • Dynatrace
  • Splunk

Pick the move you are planning

Each guide covers one move: the documented method, what to check before you start, the phases and the cutover. Where a method has a pause or a version limit, the guide says so and links to the engine's own documentation.

The eight moves side by side

The method decides how close a move gets to zero downtime. Replication-based methods keep the old and new side live until the switch, while a dump and restore needs a pause, so the design review picks a replication method wherever the engine documents one.

MoveDocumented methodBoth sides live before the switchOfficial docs
Amazon MQ to RabbitMQDefinitions import, federation, shovel; the RabbitMQ blue-green methodYes: federation and shovel carry messagesRabbitMQ docs
Amazon RDS to PostgreSQLLogical replication; pg_dump and pg_restore for the schemaYes with logical replication, no with a dump alonePostgreSQL docs
Redis to ValkeyReplication with REPLICAOF; RDB snapshot copyYes with replication, no with a snapshot copyValkey docs
Atlas to self-managed MongoDBmongosync; mongodump and mongorestoreYes with mongosync until commit, no with mongodumpMongoDB docs
Oracle to PostgreSQLora2pg for schema and data; change capture for live changesOnly when a change-capture tool is addedora2pg docs
MySQL to PostgreSQLpgloader for the load; Debezium for live changesOnly when a change-capture tool is addedpgloader docs
Confluent to Apache KafkaMirrorMaker 2Yes: it replicates continuouslyApache Kafka docs
Elasticsearch to OpenSearchRemote reindex; snapshot restore; Migration AssistantYes with remote reindex or Migration Assistant; snapshot restore needs downtime or change captureOpenSearch docs

Sources: the engine documentation linked in each row and in each guide; checked 30 Oct 2026.

How it works

What owning the cutover means

We run the migration and own the cutover, with both sides live until you switch. Zero downtime is the plan.

  1. Review

    An engineer reviews the current setup: sizes, settings, versions, traffic and the limits the source service enforces.

  2. Design

    The new cluster and the migration method are written down and signed off before anything is built.

  3. Link both sides

    The documented method keeps the old and new side in step while both stay live.

  4. Cut over

    Traffic switches only when the new side is verified, and the old side stays until you are sure.

The timeline and runbook for each engine's migration are written in the design step, from your data volume, traffic and change windows, and you approve them before the cutover is scheduled.

Operated by AceMQ

Who runs the migration

AceMQ engineers run every move. AceMQ has operated open source data and messaging systems for 10+ years and serves 160+ customers, with engineers on call 24/7.

Operated by AceMQCompany figures, as published on acemq.com
160+customers served by AceMQ, which operates OSStend
10+years running open source data and messaging
24/7on-call engineers, not a ticket queue
Insurance · named reference

IBM MQ to RabbitMQ, without replacing the core

American National Insurance moved its Windows-based IBM MQ queues to RabbitMQ on Kubernetes first, with both brokers live until behaviour was validated, while IBM MQ licensing costs were progressively removed. Use case on acemq.com.

AceMQ engagement
Insurance · named reference

A Kafka CDC pipeline it did not need

American National replaced a Kafka-based change data capture pipeline for SQL Server with standalone Debezium publishing to RabbitMQ, removing Kafka clusters and Kafka Connect the use case did not need. Use case on acemq.com.

AceMQ engagement

AceMQ names a customer only with that customer's written permission, so most of this record stays anonymous. Ask for a similar workload in the 45-minute review.

FAQ

Questions about migration

Talk to an engineer →

Does every migration have zero downtime?

Zero downtime is the plan for each move, and the method decides how close it gets. Replication-based methods keep both sides live. A dump and restore needs a pause, so the design review picks a replication method wherever the engine documents one.

Can the migration be run without OSStend?

Yes. Each guide links to the engine's own documentation, and the methods work without OSStend. The guides also say where a move needs care, so a team that runs it alone can plan for it.

How long does a migration take?

Duration depends on data volume, change rate, the number of applications and how long both sides must stay live. An engineer gives an estimate for the specific workload during the design review.

Talk to an engineer

Bring the move you are planning

45 minutes with an engineer: the current setup is reviewed against the documented method and the cutover is sketched. No ticket queue.

  • A design sketch for your workload, not a plan menu
  • A zero-downtime cutover path for what you run today
  • A price for that design, after the review
See pricing →

Your request goes to the OSStend team. No newsletter sign-up.

Get a quoteTalk to an engineer
2Engines
3Where should it run?
4What do you need?

Your request goes to the OSStend team. No newsletter sign-up.