Skip to content

Commit 5b25412

Browse files
kodster28RebeccaTamachiro
authored andcommitted
[Pages] Clarify vercel migration guide (#21605)
* [Pages] Clarify vercel migration guide * Update src/content/docs/pages/migrations/migrating-from-vercel/index.mdx
1 parent b29af71 commit 5b25412

File tree

3 files changed

+44
-31
lines changed

3 files changed

+44
-31
lines changed

src/content/docs/pages/configuration/custom-domains.mdx

+4-15
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,15 @@
11
---
22
pcx_content_type: how-to
33
title: Custom domains
4-
54
---
65

6+
import { Render } from "~/components";
7+
78
When deploying your Pages project, you may wish to point custom domains (or subdomains) to your site.
89

910
## Add a custom domain
1011

11-
To add a custom domain:
12-
13-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
14-
2. Select your account in **Account Home** > **Workers & Pages**.
15-
3. Select your Pages project > **Custom domains**.
16-
4. Select **Set up a domain**.
17-
5. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
18-
19-
![Adding a custom domain for your Pages project through the Cloudflare dashboard](~/assets/images/pages/platform/domains.png)
12+
<Render file="custom-domain-steps" />
2013

2114
### Add a custom apex domain
2215

@@ -32,10 +25,8 @@ If you are deploying to a subdomain, it is not necessary for your site to be a C
3225

3326
:::note
3427

35-
3628
If the zone is on the Enterprise plan, make sure that you [release the zone hold](/fundamentals/setup/account/account-security/zone-holds/#release-zone-holds) before adding the custom domain. A zone hold would prevent the custom subdomain from activating.
3729

38-
3930
:::
4031

4132
#### Add a custom CNAME record
@@ -50,10 +41,8 @@ If your site is already managed as a Cloudflare zone, the CNAME record will be a
5041

5142
:::note
5243

53-
5444
To ensure a custom domain is added successfully, you must go through the [Add a custom domain](#add-a-custom-domain) process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a [`522` error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out).
5545

56-
5746
:::
5847

5948
## Delete a custom domain
@@ -115,4 +104,4 @@ Once a custom domain is set up, if you change the DNS entry to point to somethin
115104

116105
## Relevant resources
117106

118-
* [Debugging Pages](/pages/configuration/debugging-pages/) - Review common errors when deploying your Pages project.
107+
- [Debugging Pages](/pages/configuration/debugging-pages/) - Review common errors when deploying your Pages project.
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,19 @@
11
---
2-
updated: 2020-09-23
2+
updated: 2025-04-10
33
difficulty: Beginner
44
pcx_content_type: tutorial
55
title: Migrating from Vercel to Pages
66
sidebar:
77
hidden: true
88
---
99

10-
In this tutorial, you will learn how to deploy your Vercel application to Cloudflare Pages.
10+
import { Render } from "~/components";
1111

12-
:::note
12+
In this tutorial, you will learn how to deploy your Vercel application to Cloudflare Pages.
1313

1414
You should already have an existing project deployed on Vercel that you would like to host on Cloudflare Pages. Features such as Vercel's serverless functions are currently not supported in Cloudflare Pages.
1515

16-
:::
17-
18-
## Finding your build command and build directory
16+
## Find your build command and build directory
1917

2018
To move your application to Cloudflare Pages, you will need to find your build command and build directory. Cloudflare Pages will use this information to build your application and deploy it.
2119

@@ -31,26 +29,39 @@ Find the **Build & Development settings** panel, which will have the **Build Com
3129

3230
![Finding the Build Command and Output Directory fields](~/assets/images/pages/migrations/vercel-deploy-3.png)
3331

34-
## Creating a new Pages project
32+
## Create a new Pages project
3533

3634
After you have found your build directory and build command, you can move your project to Cloudflare Pages.
3735

3836
The [Get started guide](/pages/get-started/) will instruct you how to add your GitHub project to Cloudflare Pages.
3937

40-
## Adding a custom domain
38+
## Add a custom domain
4139

42-
To use a custom domain for your Pages project, [add a custom domain](/pages/configuration/custom-domains/) that is the same custom domain as your currently deployed Vercel application. When Pages finishes the initial deploy of your site, you will need to delete the Vercel application to start sending requests to Cloudflare Pages.
40+
Next, connect a [custom domain](/pages/configuration/custom-domains/) to your Pages project. This domain should be the same one as your currently deployed Vercel application.
4341

44-
:::note
42+
### Change domain nameservers
4543

46-
Cloudflare does not provide IP addresses for your Pages project because we do not require `A` or `AAAA` records to link your domain to your project. Instead, Cloudflare uses `CNAME` records.
44+
In most cases, you will want to [add your domain to Cloudflare](/dns/zone-setups/full-setup/setup/).
4745

48-
For more details, refer to [Custom domains](/pages/configuration/custom-domains/).
46+
This does involve changing your domain nameservers, but simplifies your Pages setup and allows you to use an apex domain for your project (like `example.com`).
47+
48+
If you want to take a different approach, read more about [custom domains](/pages/configuration/custom-domains/).
49+
50+
### Set up custom domain
4951

50-
:::
52+
<Render file="custom-domain-steps" />
5153

52-
## Cleaning up your old application and assigning the domain
54+
The next steps vary based on if you [added your domain to Cloudflare](#change-domain-nameservers):
5355

54-
In your DNS settings for your domain, make sure that you have updated the CNAME record for your domain from Vercel to Cloudflare Pages. With your DNS record updated, requests will go to your Pages application.
56+
- **Added to Cloudflare**: Cloudflare will set everything up for you automatically and your domain will move to an `Active` status.
57+
- **Not added to Cloudflare**: You need to [update some DNS records](/pages/configuration/custom-domains/#add-a-custom-subdomain) at your DNS provider to finish your setup.
5558

56-
By completing this guide, you have successfully migrated your Vercel project to Cloudflare Pages.
59+
## Delete your Vercel app
60+
61+
Once your custom domain is set up and sending requests to Cloudflare Pages, you can safely delete your Vercel application.
62+
63+
## Troubleshooting
64+
65+
Cloudflare does not provide IP addresses for your Pages project because we do not require `A` or `AAAA` records to link your domain to your project. Instead, Cloudflare uses `CNAME` records.
66+
67+
For more details, refer to [Custom domains](/pages/configuration/custom-domains/).
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
---
2+
{}
3+
---
4+
5+
To add a custom domain:
6+
7+
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
8+
2. Select your account in **Account Home** > **Workers & Pages**.
9+
3. Select your Pages project > **Custom domains**.
10+
4. Select **Set up a domain**.
11+
5. Provide the domain that you would like to serve your Cloudflare Pages site on and select **Continue**.
12+
13+
![Adding a custom domain for your Pages project through the Cloudflare dashboard](~/assets/images/pages/platform/domains.png)

0 commit comments

Comments
 (0)