diff --git a/website-1.x/blog/2021-11-05-algolia-migration.md b/website-1.x/blog/2021-11-05-algolia-migration.md
index 4926e1d708..37c7949150 100644
--- a/website-1.x/blog/2021-11-05-algolia-migration.md
+++ b/website-1.x/blog/2021-11-05-algolia-migration.md
@@ -11,11 +11,13 @@ image: /img/blog/2021-05-12-announcing-docusaurus-two-beta/social-card.png
 
 Algolia DocSearch is migrating to a new system.
 
-Docusaurus v1 sites should upgrade too or search will stop working.
+Docusaurus v1 sites should upgrade their configuration.
 
 <!--truncate-->
 
-From now on, it is required to use an `appId` in your Docusaurus v1 site configuration:
+Algolia will stop crawling and updating your existing index soon, potentially leading to stale search results.
+
+From now on, it will be required to use an `appId` in your Docusaurus v1 site configuration:
 
 ```js
 const siteConfig = {
@@ -28,8 +30,6 @@ const siteConfig = {
 module.exports = siteConfig;
 ```
 
-You should have received an `appId` + `apiKey` by email with an invitation to join the Algolia SaaS application.
+The migration will roll out in batches, and you should receive a new `appId` and `apiKey` by email soon, with an invitation to join the Algolia SaaS application.
 
-If you didn't receive any email, please reach out to the Algolia DocSearch support team and they'll invite you.
-
-Further information will be provided on the Docusaurus v2 blog.
+More information can be found in on the [DocSearch migration page](https://docsearch.algolia.com/docs/migrating-from-legacy) and we will publish a [Docusaurus v2 blog post](https://v2.docusaurus.io/blog).