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 mailopost: stop and continue any time
  • Data moves in batches — big indexes don't choke
  • Completion is explicit and visible

How it works

To connect mailopost and , you don't need a developer: a ready-made scenario links them in minutes.

  1. Starts when: Schedule Trigger
  2. Then: Parameters
  3. Then: Get Next Page Token
  4. Check: Is Next Pagination Token null?
  5. If yes: First Iteration?
  6. If yes: Get Record First Page
  7. Then: Save Next Page Token
  8. Then: Select Ids
  9. Then: Prepare Fetch Body
  10. Then: Fetch Vectors
  11. Then: Format2Weaviate
  12. Then: LoadWeAviate
  13. If no: Get Record Next Page
  14. Then: Save Next Page Token1
  15. Then: Select Ids1

You can launch this integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.