Kvindo™ Cloud Docs
This section covers moving existing data into a Kvindo Cloud service. Each guide takes one service and walks through the same three phases: copy the data across, prove the copy is complete, then cut your application over — with a rollback that works if the cutover goes wrong.
• OpenSearch — moving indices from another cluster into a Kvindo Cloud OpenSearch cluster
• The copy can be re-run. A migration that has to be restarted from zero after an interruption is a migration you cannot schedule. Every guide writes documents under the same identifier the source used, so running it twice overwrites rather than duplicates, and progress is checkpointed per index so a failure resumes instead of restarting.
• The cutover can be rolled back. The copy only ever reads from the source, never writes to it. That means any failure before your application is pointed at the new service is recoverable by pointing it back — the old data is still there, untouched, and the copy can be resumed the next day.
Decide when to stop your writers. Every guide asks you to quiesce the source before the final pass and gives you a way to prove it is actually quiet — but the moment to do that, and how long you can afford it, is your call, not the platform's.
More in this section