ais migration

Author: aninibread

src/content/docs/ai-search/configuration/data-source/built-in-storage.mdx

@@ -20,7 +20,7 @@ Instances created before this date do not include built-in storage and do not su
 
 <DashButton url="/?to=/:account/ai/ai-search" />
 
-All instances will be migrated to managed infrastructure. Migration details are coming soon.
+All instances created before this date will be automatically migrated to managed infrastructure on **June 3, 2026**. For details, refer to [Limits & pricing](/ai-search/platform/limits-pricing/#previous-instances).
 
 ## Upload and manage files
 

src/content/docs/ai-search/configuration/indexing/vector-search.mdx

@@ -14,7 +14,7 @@ Vector search converts your query into a vector embedding and finds chunks with
 
 Instances created after **April 16, 2026** include a built-in vector index powered by [Vectorize](/vectorize/). The vector index stores embeddings generated from your content and is created and maintained automatically. You do not need to create or manage a Vectorize index yourself.
 
-Instances created before this date use a Vectorize index provisioned on your account. These instances are billed separately for Vectorize usage. All instances will be migrated to managed infrastructure. Migration details are coming soon.
+Instances created before this date use a Vectorize index provisioned on your account. These instances are billed separately for Vectorize usage. All instances created before this date will be automatically migrated to managed infrastructure on **June 3, 2026**. For details, refer to [Limits & pricing](/ai-search/platform/limits-pricing/#previous-instances).
 
 ## Embedding model
 

src/content/docs/ai-search/platform/limits-pricing.mdx

@@ -32,7 +32,7 @@ To request an adjustment to a limit, complete the [Limit Increase Request Form](
 
 ## Previous instances
 
-If your instance was created before **April 16, 2026**, it provisions and runs on top of Cloudflare services in your account. AI Search is free to enable. You are billed for the underlying services it provisions on your account:
+If your instance was created before **April 16, 2026**, it provisions and runs on top of Cloudflare services in your account. These instances will be automatically migrated to managed infrastructure on **June 3, 2026** and the [New instances](#new-instances) limits will apply. You are billed for the underlying services until migration is completed:
 
 | Service                                      | Description                                                 |
 | -------------------------------------------- | ----------------------------------------------------------- |
@@ -52,6 +52,13 @@ The following limits apply to these instances:
 | Max custom metadata fields          | 5 per AI Search instance |
 | Max text metadata value length      | 500 characters           |
 
-All instances will be migrated to managed infrastructure. Migration details are coming soon.
+### Migration to managed infrastructure
 
-For more information about how each service is used, refer to [How AI Search works](/ai-search/concepts/how-ai-search-works/).
+The migration will begin on **June 3, 2026** and may take up to three days. No downtime is expected and no action is required. The following changes will apply:
+
+- **Vectorize database**: Vectors generated by an AI Search instance will be automatically moved from the associated Vectorize database in your account to a managed vector database in the instance. Once the migration is verified, the legacy Vectorize database will be deleted from your account automatically.
+- **R2 as data source**: If your instance uses an R2 bucket as a data source, this remains unchanged. Your instance will also get built-in managed storage for direct file uploads.
+- **Website as data source**: If your instance uses a website as a data source, previously crawled webpages will be moved to built-in storage, and all future crawls will be stored there. The previous R2 bucket will remain in your account. Browser Rendering is now built into the product so you will no longer be billed separately for Browser Rendering usage from AI Search.
+- **Workers AI and AI Gateway**: These remain separate services. Your existing usage, configurations, and billing for Workers AI and AI Gateway are unchanged.
+
+You can identify which instance is still on legacy infrastructure in the dashboard under **AI** > **AI Search**. If the instance does not have a **Built-in Storage** label, it will be migrated to the new infrastructure.

src/content/release-notes/ai-search.yaml

@@ -3,6 +3,10 @@ link: "/ai-search/platform/release-note/"
 productName: AI Search
 productLink: "/ai-search/"
 entries:
+  - publish_date: "2026-05-12"
+    title: Automatic migration to managed infrastructure on June 3, 2026
+    description: |-
+      Instances created before April 16, 2026 will be automatically migrated to managed infrastructure on **June 3, 2026**. The migration may take up to three days with no service downtime expected. No action is required. After migration, instances will include built-in storage, a built-in vector index, and built-in web crawling, and [new limits](/ai-search/platform/limits-pricing/#new-instances) will apply. For full migration details, refer to [Limits & pricing](/ai-search/platform/limits-pricing/#previous-instances).
   - publish_date: "2026-04-16"
     title: Hybrid search
     description: |-