Migrate from Algolia
Import records, review mappings and move the website connection when the results are ready.
Algolia migration prepares content for a selected SiteOS index. Start with a separate empty named index if you want to evaluate the migration without replacing existing SiteOS content. For a feature and pricing comparison before you start, see SiteOS vs Algolia.
Connect an index or upload records
Choose Migrate from Algolia in setup or Content → Add content. A direct connection uses your Algolia Application ID and a temporary key with browse and settings access. listIndexes is optional: without it, provide the exact index name. You do not need an account password or an admin key.
The browser connects directly to Algolia for this flow. Inspect the sample records and map the title, searchable text, URL and section fields. The initial sample helps choose the mapping; it is not the complete export. The review stage reads the selected index’s records and available configuration.
Alternatively, upload a supported records export. The records-only upload does not import separate settings or synonym files automatically.
Review what will transfer
Check real result titles, complete body text, relative-URL resolution and section destinations. Review the complete import counts and source conflicts before applying it.
A full replacement affects the selected SiteOS index. Include its other sources if they must remain, or migrate into a new index instead. Review does not change the published SiteOS index, and migration does not delete the Algolia source.
Keep a copy of the original export and the migration report. The connected workflow provides an archive of the exported records and configuration for review.
Work with exported configuration
The CLI’s offline preparation supports records plus optional settings, synonyms and rules files. Search skills help your agent inspect these inputs and prepare a mapping before anything is published.
Supported synonym forms can be translated into SiteOS settings within its limits. Review the proposed settings in Relevance. Algolia-specific ranking rules, replicas, facets, personalization and historical analytics do not transfer automatically. Retaining a rules file in the archive is not the same as applying it.
Offline preparation supports up to 100,000 records and 100 MB per input file, with a 100 MB prepared-content limit. Large imports use a staged upload followed by review; do not split one full replacement into sequential partial replacements.
Change the website connection last
After publication, compare representative queries in Playground and check destination links. Adapt the website to SiteOS’s query, suggestions and analytics integration, then verify a real visitor journey.
The website continues to use Algolia until you change its integration. Keep the old connection available until the new one has been checked. Revoke the temporary export key when it is no longer needed; do not put it in prompts, public examples or repository files.
Continue with Website connection and Search relevance.