The export endpoint transfers data directly from one Meilisearch instance to another over the network. Unlike dumps, which create a file on disk that you must manually move, exports push data straight to a remote instance in a single operation.Documentation Index
Fetch the complete documentation index at: https://www.meilisearch.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
When to use exports
- Environment migration: Move data from a staging instance to production (or vice versa).
- Creating replicas: Set up a second instance with the same data for redundancy or load distribution.
- Scaling: Transfer indexes to a larger instance when your data outgrows the current one.
Export data to a remote instance
Send aPOST request to /export on the source instance, specifying the destination URL and (optionally) an API key:
Monitor the export task
The export runs asynchronously. Use the task UID to check its progress:succeeded, all data has been transferred to the destination instance.
Export vs. dumps
| Export | Dump | |
|---|---|---|
| Mechanism | Direct network transfer to a remote instance | Creates a file on the source instance’s disk |
| Best for | Live migration between running instances | Backups, version upgrades, offline transfers |
| Requires | Network access to the destination | File system access to move the dump file |
Next steps
Export API reference
Full API reference for the export endpoint
Monitor tasks
Track the status of asynchronous operations
Indexing overview
Learn more about how indexing works in Meilisearch