Add VRF → CRE migration guide

src/config/sidebar.ts

@@ -778,6 +778,11 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           url: "cre/reference/clf-migration",
           highlightAsCurrent: ["cre/reference/clf-migration-ts", "cre/reference/clf-migration-go"],
         },
+        {
+          title: "Migrate from Chainlink VRF",
+          url: "cre/reference/vrf-migration",
+          highlightAsCurrent: ["cre/reference/vrf-migration-ts", "cre/reference/vrf-migration-go"],
+        },
       ],
     },
   ],

src/content/vrf/index.mdx

@@ -13,6 +13,13 @@ metadata:
 import Vrf2_5Common from "@features/vrf/v2-5/Vrf2_5Common.astro"
 import { Aside } from "@components"
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment. For new integrations, start with CRE and use the
+  [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a workflow.
+</Aside>
+
 <Vrf2_5Common callout="security" />
 
 **Chainlink VRF (Verifiable Random Function)** is a provably fair and verifiable random number generator (RNG) that enables smart contracts to access random values without compromising security or usability. For each request, Chainlink VRF generates one or more random values and cryptographic proof of how those values were determined. The proof is published and verified onchain before any consuming applications can use it. This process helps ensure that results cannot be tampered with or manipulated by any single entity including oracle operators, smart contract developers, users, miners, or block builders\*.

src/content/vrf/llms-full.txt

@@ -1,7 +1,12 @@
 # Chainlink VRF
 Source: https://docs.chain.link/vrf
 
-<Vrf2_5Common callout="security" />
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment. For new integrations, start with CRE and use the
+  [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a workflow.
+</Aside>
 
 **Chainlink VRF (Verifiable Random Function)** is a provably fair and verifiable random number generator (RNG) that enables smart contracts to access random values without compromising security or usability. For each request, Chainlink VRF generates one or more random values and cryptographic proof of how those values were determined. The proof is published and verified onchain before any consuming applications can use it. This process helps ensure that results cannot be tampered with or manipulated by any single entity including oracle operators, smart contract developers, users, miners, or block builders\*.
 
@@ -62,6 +67,13 @@ To learn when VRF v2.5 becomes available on more networks, follow us on [Twitter
 # Getting Started with Chainlink VRF V2.5
 Source: https://docs.chain.link/vrf/v2-5/getting-started
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment. For new integrations, start with CRE and use the
+  [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a workflow.
+</Aside>
+
 <Aside type="note" title="Requirements">
   This guide assumes that you have basic knowledge about writing and deploying smart contracts. If you are new to smart
   contract development, learn how to [Deploy Your First Smart Contract](/quickstarts/deploy-your-first-contract) before
@@ -605,6 +617,14 @@ Source: https://docs.chain.link/vrf/v2-5/migration-from-v2
 
 <Vrf2_5Common callout="security" />
 
+<Aside type="tip" title="Migrating anyway? Consider Chainlink CRE instead">
+  If you're updating your integration, consider migrating straight to [Chainlink CRE](/cre) instead of VRF v2.5. CRE
+  generates randomness the same DON-secured way as VRF, but as one capability inside a workflow that can also read
+  onchain state, call external APIs, run your own logic, and write results to multiple chains from a single deployment.
+  See the [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a
+  workflow.
+</Aside>
+
 VRF V2.5 replaces both VRF V1 and VRF V2 on November 29, 2024. [Learn more about VRF V2.5](https://blog.chain.link/introducing-vrf-v2-5/).
 
 ## Benefits of VRF v2.5
@@ -1036,6 +1056,14 @@ Source: https://docs.chain.link/vrf/v2-5/migration-from-v1
 
 <Vrf2_5Common callout="security" />
 
+<Aside type="tip" title="Migrating anyway? Consider Chainlink CRE instead">
+  If you're updating your integration, consider migrating straight to [Chainlink CRE](/cre) instead of VRF v2.5. CRE
+  generates randomness the same DON-secured way as VRF, but as one capability inside a workflow that can also read
+  onchain state, call external APIs, run your own logic, and write results to multiple chains from a single deployment.
+  See the [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a
+  workflow.
+</Aside>
+
 VRF V2.5 replaces both VRF V1 and VRF V2 on November 29, 2024. [Learn more about VRF V2.5](https://blog.chain.link/introducing-vrf-v2-5/).
 
 ## Comparing VRF v1 to VRF v2.5
@@ -1885,6 +1913,14 @@ Source: https://docs.chain.link/vrf/v2-5/overview/subscription
 
 <Vrf2_5Common callout="security" />
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment — no subscription to fund. For new integrations, start
+  with CRE and use the [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing
+  request/fulfill flow to a workflow.
+</Aside>
+
 This section explains how to generate random numbers using the subscription method.
 
 <Aside type="note" title="Migrate to V2.5">
@@ -2015,6 +2051,13 @@ You can see the configuration for each network on the [Supported networks](/vrf/
 # Direct Funding Method
 Source: https://docs.chain.link/vrf/v2-5/overview/direct-funding
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment. For new integrations, start with CRE and use the
+  [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a workflow.
+</Aside>
+
 This guide explains how to generate random numbers using the *direct funding* method. This method doesn't require a subscription and is optimal for one-off requests for randomness. This method also works best for applications where your end-users must pay the fees for VRF because the cost of the request is determined at request time.
 
 <Aside type="note" title="Migrate to V2.5">

src/content/vrf/v2-5/getting-started.mdx

@@ -17,6 +17,13 @@ metadata:
 
 import { Aside, CodeSample, ClickToZoom } from "@components"
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment. For new integrations, start with CRE and use the
+  [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a workflow.
+</Aside>
+
 <Aside type="note" title="Requirements">
   This guide assumes that you have basic knowledge about writing and deploying smart contracts. If you are new to smart
   contract development, learn how to [Deploy Your First Smart Contract](/quickstarts/deploy-your-first-contract) before

src/content/vrf/v2-5/migration-from-v1.mdx

@@ -10,6 +10,14 @@ import { Tabs, TabsContent } from "@components/Tabs"
 
 <Vrf2_5Common callout="security" />
 
+<Aside type="tip" title="Migrating anyway? Consider Chainlink CRE instead">
+  If you're updating your integration, consider migrating straight to [Chainlink CRE](/cre) instead of VRF v2.5. CRE
+  generates randomness the same DON-secured way as VRF, but as one capability inside a workflow that can also read
+  onchain state, call external APIs, run your own logic, and write results to multiple chains from a single deployment.
+  See the [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a
+  workflow.
+</Aside>
+
 VRF V2.5 replaces both VRF V1 and VRF V2 on November 29, 2024. [Learn more about VRF V2.5](https://blog.chain.link/introducing-vrf-v2-5/).
 
 ## Comparing VRF v1 to VRF v2.5

src/content/vrf/v2-5/migration-from-v2.mdx

@@ -10,6 +10,14 @@ import { Tabs, TabsContent } from "@components/Tabs"
 
 <Vrf2_5Common callout="security" />
 
+<Aside type="tip" title="Migrating anyway? Consider Chainlink CRE instead">
+  If you're updating your integration, consider migrating straight to [Chainlink CRE](/cre) instead of VRF v2.5. CRE
+  generates randomness the same DON-secured way as VRF, but as one capability inside a workflow that can also read
+  onchain state, call external APIs, run your own logic, and write results to multiple chains from a single deployment.
+  See the [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a
+  workflow.
+</Aside>
+
 VRF V2.5 replaces both VRF V1 and VRF V2 on November 29, 2024. [Learn more about VRF V2.5](https://blog.chain.link/introducing-vrf-v2-5/).
 
 ## Benefits of VRF v2.5

src/content/vrf/v2-5/overview/direct-funding.mdx

@@ -15,6 +15,13 @@ metadata:
 import VrfCommon from "@features/vrf/v2/common/VrfCommon.astro"
 import { Aside, ClickToZoom } from "@components"
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment. For new integrations, start with CRE and use the
+  [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing request/fulfill flow to a workflow.
+</Aside>
+
 This guide explains how to generate random numbers using the _direct funding_ method. This method doesn't require a subscription and is optimal for one-off requests for randomness. This method also works best for applications where your end-users must pay the fees for VRF because the cost of the request is determined at request time.
 
 <Aside type="note" title="Migrate to V2.5">

src/content/vrf/v2-5/overview/subscription.mdx

@@ -14,6 +14,14 @@ import { YouTube } from "@astro-community/astro-embed-youtube"
 
 <Vrf2_5Common callout="security" />
 
+<Aside type="tip" title="Building something new? Use Chainlink CRE">
+  [Chainlink CRE](/cre) is our upgrade path for onchain randomness. CRE generates randomness the same DON-secured way as
+  VRF, but as one capability inside a workflow that can also read onchain state, call external APIs, run your own logic,
+  and write results to multiple chains from a single deployment — no subscription to fund. For new integrations, start
+  with CRE and use the [VRF-to-CRE migration guide](/cre/reference/vrf-migration-ts) to map your existing
+  request/fulfill flow to a workflow.
+</Aside>
+
 This section explains how to generate random numbers using the subscription method.
 
 <Aside type="note" title="Migrate to V2.5">