Vector index migration between services — no recomputation

The scenario moves records from one vector store to another in batches, remembering where it left off. The existing data travels as-is — no recomputation.

  • Migrate without recomputing — that's real money saved
  • The resume marker lives in Airtable: stop and continue any time
  • Data moves in batches — big indexes don't choke
  • Completion is explicit and visible