Migrate from Algolia to Meilisearch on Layerbase
Move an Algolia index to managed Meilisearch on Layerbase in one guided pass. We copy your records and translate your searchable attributes, ranking, faceting, and synonyms. Read-once, your Algolia app is never modified.
Why switch
Why teams leave Algolia
Settings translated, not just records
We copy your records and translate your searchable attributes, ranking rules, faceting, and synonyms into their Meilisearch equivalents, then show you a review report of exactly what mapped.
Flat pricing, no per-search billing
Meilisearch on Layerbase costs the same however hard you search it. No per-record or per-request meters, and the engine itself is open source.
Fast, typo-tolerant search out of the box
Meilisearch gives you instant search-as-you-type with typo tolerance by default, plus filtering and faceting, behind a simple REST API and official SDKs.
How it works
Four steps, one pass
- 1
Create a free account or sign in
Sign in with Google or GitHub. No credit card is needed to start, and the migration wizard opens with this platform already selected.
- 2
Connect your account
Paste your Algolia Application ID and an Admin API key (Algolia dashboard, then Settings, then API Keys). We list your indexes so you can pick one, then copy its records and translate its searchable attributes, ranking, faceting, and synonyms into Meilisearch. A Search-only key will not work: browsing records and reading settings needs an Admin key.
- 3
Pick what to migrate and name it
Choose what to bring over, give the new Layerbase database a name, and start the migration. Progress streams live in the dashboard.
- 4
We copy it in one pass
The migration reads from Algolia once and never writes to it. Credentials are used for the copy and never stored. When it finishes, you land in your new database with a live TLS connection string.
Questions
Common Algolia migration questions
What key do I need?+
Your Algolia Application ID and an Admin API key (Algolia dashboard, then Settings, then API Keys). A Search-only key will not work: browsing records and reading settings needs an Admin key. It is used once and never stored.
What translates and what does not?+
Records copy as-is. Searchable attributes, ranking, faceting, and synonyms are translated into their Meilisearch equivalents. Features without a Meilisearch counterpart are listed in the review report you see when the migration finishes, so nothing silently disappears.
Will my Algolia app be modified?+
No. The migration browses your index read-only, copies what it finds, and disconnects. Your Algolia app keeps serving queries throughout.
Do my search clients need to change?+
Yes: Meilisearch has its own API and SDKs (JavaScript, PHP, Python, and more). The query model is similar, so most integrations port quickly, and the review report tells you which settings behave differently.
Ready to leave Algolia?
Sign in, and the migration wizard opens with Algolia already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.