Nitin Pakhide published An Upgrade to the latest web technologies on 18 March 2024. He last updated the page on 7 September 2026. This is his own post for ShikhaShikz, not a Vercel page.
The article is mostly a WordPress-to-Astro rebuild. The hosting moves sit in two dated updates at the bottom. On 27 June 2024 the Astro site left Netlify for Vercel. On 23 October 2024 it left Vercel for Cloudflare. He writes a few sentences for each hop. He does not describe a dump, a DNS cutover, or a rollback.
If you are looking at the first hop, start with the Netlify → Vercel playbook. Vercel’s migrate-from-Netlify guide is the checklist for build settings, env vars, redirects, headers, and Functions. Nitin’s post is the pricing field report. It is not a cutover diary.
Why they left Netlify
The new site was Astro with Tailwind, GitHub, and Markdown. He used the free Pinwheel Astro theme. The old WordPress site stayed at shikhashikz.co.in. An earlier Jekyll site still sits on GitHub Pages at shikhashikz.in.
Netlify was the first host for the Astro site. He had already tried Amazon Amplify and called it raw. Netlify felt smooth. The free plan he cited was a single user with up to 100 GB of bandwidth a month. That matches Netlify’s legacy Free row: one free member, 100 GB, and a hard bandwidth cap.
He still warned about the paid step. GitHub plus a paid Netlify plan, he wrote, can get expensive for an organization.
The June 2024 update is one paragraph. Netlify had been “fantastic with no issues.” They switched because Netlify’s pricing “charges per GitHub user, unlike Vercel.”
That sentence needs the 2024 price list next to it. On the legacy Pro plan Netlify billed $19 a month per member, and that count included active Git Contributors. A Netlify support thread from 2023 says those extra seats apply to private repos. Public-repo commits did not add seats. He does not say whether shikhashikz.com was private, how many people committed, or what the invoice was. I am not inventing a number.
He does not publish a Vercel quote from June 2024 either. Vercel’s own Vercel vs Netlify page later lists Pro at $20 a month per seat, with free Viewer seats. Both hosts had a per-person line. The labels differed: Git Contributors on Netlify Pro, team seats on Vercel Pro.
How they moved
He does not describe the Vercel project, the build command, or the DNS flip. The site already lived in GitHub, so a new Git host is the usual path. That is also the first step in Vercel’s migrate guide: create the project, copy base / build / publish settings from the Netlify UI or netlify.toml, then copy env vars.
Vercel will not read netlify.toml. Redirects and headers move into vercel.json, or into the framework config. Functions move from functions/ to api/ and change signature. He never says the Astro site had any of those. A marketing site on a theme often does not.
He also does not describe a dual-run or a rollback window. Vercel documents an incremental migration if you want to move routes in pieces. There is no sign they used it.
Four months later they moved again. The 23 October 2024 update says Vercel performance and collaboration were fine, and that cost rose with each extra team member. Cloudflare’s “unlimited collaboration at no additional cost” is the reason he gives for the second hop. I fetched shikhashikz.com in October 2026. The response still comes from Cloudflare.
If that second hop is your route, the matching page here is the Vercel → Cloudflare Pages playbook.
What they gained
On Netlify he already had Git deploys and a free bandwidth cap he was comfortable with. The Vercel move did not come with a speed chart, a new feature, or a published invoice.
What he wanted was a host that would not bill extra GitHub users. He does not say the Vercel bill was lower. The October update is the outcome we have: the per-person problem showed up on Vercel too, and they left.
The later Cloudflare hop is the one he calls more flexible and cost-effective. He does not publish that bill either.
Netlify’s current credit-based Pro plan advertises unlimited members and no per-seat charge for Git contributors. That is 2025 and 2026 pricing, after a 4 September 2025 change for new accounts. It is not the list he was reading in June 2024. Do not use today’s marketing page to judge his move.
What broke or got skipped
This write-up skips the cutover. No downtime, no redirect table, no env-var list, no preview URL. If your site has Forms, Identity, Netlify Functions, or a long _redirects file, his path does not tell you what happened to them.
He also does not say they exported Netlify analytics, form submissions, or deploy history. Those stay in the old project.
The June claim that Vercel does not charge per GitHub user did not survive contact with a growing team. Per-seat and per-contributor are different words for a similar invoice once more people touch the repo.
The WordPress and Jekyll sites were not part of this host swap. They stayed on their own hosts.
What I would copy
Treat his June update as a pricing note, not as a migration runbook. Run the Netlify → Vercel playbook for the actual move.
Write down how the host counts people before you switch. Ask whether a Git push on a private repo creates a billable seat. Ask whether a designer who only leaves comments is free. Netlify’s 2024 Git Contributor rule and Vercel’s seat-plus-Viewer split answer those questions differently.
Keep the old project billed and serving until the new custom domain answers. He never says he did that. I would.
If the only reason to move is the seat model, read the current price pages on the day you move. Both vendors have changed the story since 2024.
And plan for a second hop. This site went Netlify to Vercel to Cloudflare in four months. The repo made that cheap. Dashboard features would not have.