Best Carrd Alternatives in 2026: Features, Migration & Real Costs

Best Carrd Alternatives in 2026: Features, Migration & Real Costs

Carrd is the undisputed default for single-page websites. At $19 per year for Pro Standard, it offers an unbeatable baseline for landing pages, simple portfolios, and API-driven micro-tools. But defaults break at scale.

The breaking point usually arrives in one of a few forms: you need multi-page navigation to capture long-tail search traffic, a CMS to manage structured content, real e-commerce beyond Stripe embeds, or team collaboration that a single-editor builder can't support. When you hit these constraints, Carrd's simplicity becomes a liability.

This guide compares six Carrd alternatives in 2026 based on real pricing, architecture, migration complexity, and total cost of ownership. We skip the marketing checklists to focus on what actually happens when you move from a $19/year static builder to a professional platform.

The Carrd Architecture and Why You Outgrow It

Before evaluating alternatives, understand what you're migrating away from. Carrd is fundamentally a single-page application (SPA) builder.

When you create a "multi-page" site in Carrd, you're building a single HTML document. The "pages" are <section> elements separated by CSS IDs (e.g., #about, #contact). Carrd uses client-side JavaScript to hide and show these sections when a user clicks a navigation link. This architecture enforces hard limits that drive most migrations:

SEO ceiling. Search engine crawlers primarily index the root index.html. You cannot set unique meta titles, descriptions, or Open Graph tags per section. Your entire site competes for rankings on a single URL. Carrd allows basic meta settings at the page level, but there is no mechanism to assign structured data, hreflang tags, or section-level canonical URLs. A 10-section Carrd site has the same SEO surface area as a blank homepage.

DOM bloat and load performance. A 20-section Carrd site loads all content, images, and scripts upfront in a single document. Every section is present in the DOM whether or not a visitor ever scrolls to it. Measured against a structurally equivalent Webflow site with lazy-loaded images and per-page scripts, the Carrd equivalent consistently shows higher Total Blocking Time and larger initial payload size. There is no per-section lazy loading, route-level code splitting, or incremental static regeneration.

No relational data model. Carrd has no native CMS. You cannot create a template page and programmatically generate 50 SEO-targeted pages from a database. Workarounds using Airtable APIs exist but carry real fragility: Airtable's free tier API is rate-limited to 5 requests per second per base, and the integration breaks if field names change on the Airtable side. There is no webhook-based invalidation, so content updates require manual re-publish.

No blog or multi-page content. Carrd does not support blog functionality. If you need a blog, you must link out to an external platform like Medium or WordPress. The same limitation applies to documentation, directories, changelogs, or any content structure with depth and discrete URLs.

No native e-commerce. Carrd has no built-in commerce layer. The standard workaround is a Stripe Payment Link or Buy Button embed — a third-party hosted form that redirects to Stripe's checkout. What you lose compared to a native commerce platform: no cart state (each product requires a separate Stripe link), no subscription management UI, no tax calculation (Stripe Tax is a separate add-on with per-transaction fees), no checkout branding beyond Stripe's limited customization, and no order management dashboard inside your site. For a single digital product, this is acceptable. For anything resembling a storefront, the gaps compound quickly.

Form constraints. Carrd forms are simple and reliable but limited in logic depth. Conditional field logic, multi-step flows, advanced validation rules, and deep automation routing (e.g., branching based on submitted values) are not native features. Pro Plus adds integrations with Stripe, Zapier, Make, n8n, and Airtable, but the form itself remains structurally flat.

No membership or gated content. Carrd does not support gated content, user logins, or membership tiers. There is no session management, no protected route, and no integration with auth providers like Auth0 or Clerk.

Editor fragility. The editor has no draft-saving or autosave feature. Closing the browser tab discards unsaved work. There is no version history, no restore point, and no staging environment.

When you migrate off Carrd, you're not just changing visual builders. You're moving from a static SPA to a relational, multi-page architecture. That distinction matters for every decision downstream.

Carrd Pricing: The Baseline for Comparison

Carrd's pricing is deliberately low for a deliberately narrow product.

All paid plans are annual-only, billed upfront. A custom domain requires Pro Standard ($19/yr), not Pro Lite ($9/yr). Pro Lite primarily removes Carrd branding. Pro Plus adds advanced forms (with Stripe, Zapier, Make, n8n, and Airtable integrations), site downloads, redirects, password protection, and canonical URL control.

The free plan has a hard cap of 50 components per page — a block of text and an image each count as one component.

Because Carrd is a single-page builder with no multi-page sites, no blog, and no commerce layer to maintain, sold on annual-only billing, the pricing model makes sense. You're paying for exactly what you get: fast, contained, disposable sites.

What You Can (and Can't) Export from Carrd

Before choosing an alternative, understand the exit path. Carrd has no native export feature, no public API, and no bulk content download.

One-Way Code Download (Pro Plus Only)

Carrd allows you to download the full code of your site as a .zip containing static HTML, CSS, JS, and optimized images. The export is one-way: forms, analytics integrations, and platform-managed embeds break on export, and the downloaded code cannot be re-uploaded to Carrd. You get a useful reference for extracting text and locating high-resolution image assets, but you cannot import this HTML directly into Webflow or Framer — both require their own proprietary DOM structures.

The Airtable Route

Many advanced Carrd users bypass the platform's content limitations by using Airtable as a backend database, connected via third-party APIs or Zapier. If your site follows this pattern, the migration path is simpler: export the Airtable base as CSV and import directly into your target CMS. The Carrd site itself still requires a manual rebuild.

DOM Scraping for Agencies

If you manage dozens of Carrd sites and need to replatform them at scale, manual copy-pasting is not viable. You'll need a scraping tool to parse the live Carrd DOM, target text nodes within Carrd's standardized .container and .wrapper class structure, and output structured JSON for your new CMS.

Here is a working Cheerio script that extracts common content nodes from a rendered Carrd page:

const cheerio = require('cheerio');
const fs = require('fs');
 
// Load your scraped Carrd HTML (e.g., via curl or Puppeteer)
const html = fs.readFileSync('carrd-export.html', 'utf8');
const $ = cheerio.load(html);
 
const sections = [];
 
// Carrd sections render inside #wrapper > .container > section
$('#wrapper section').each((i, el) => {
  const id = $(el).attr('id') || `section-${i}`;
  const heading = $(el).find('h1, h2, h3').first().text().trim();
  const body = $(el).find('p').map((_, p) => $(p).text().trim()).get().join('\n');
  const images = $(el).find('img').map((_, img) => $(img).attr('src')).get();
 
  sections.push({ id, heading, body, images });
});
 
fs.writeFileSync('carrd-content.json', JSON.stringify(sections, null, 2));
console.log(`Extracted ${sections.length} sections`);

Run this against the downloaded Pro Plus HTML export or a Puppeteer-rendered snapshot of the live site. The output JSON maps directly to CMS field schemas in Webflow, Sanity, or Contentful.

What Doesn't Transfer

• Form submissions stay in Carrd's dashboard interface. Export them manually before canceling your subscription.
• Images have no bulk download. Use browser developer tools to download images from the network panel, or extract src attributes from the code export.
• Redirects and custom domains require Pro Standard or above. Free .carrd.co subdomains cannot preserve URL structure or carry link equity to a new domain.

Best Carrd Alternatives by Use Case

Here's the decision matrix before we break down each option:

Webflow: The CMS Route

Webflow is the primary destination for teams outgrowing Carrd who need a relational database, programmatic SEO, and granular CSS control. It's the closest visual approximation of writing actual frontend code.

Architecture

Webflow generates static HTML, CSS, and JavaScript at publish time but maintains a relational database (the Webflow CMS) in the editor. You create Collections (e.g., "Blog Posts," "Team Members"), define custom fields, and design a single template page that dynamically populates hundreds of unique URLs. Each Collection item gets its own discrete URL — something Carrd's section-based SPA cannot produce.

Webflow CMS supports reference fields (one-to-one links between Collection items) and multi-reference fields (one-to-many links). This enables genuine relational content structures: an "Articles" Collection referencing an "Authors" Collection and a "Categories" Collection. You can filter, sort, and paginate Collection Lists on the frontend using Webflow's native query interface.

Pricing (Post-May 2026)

Webflow overhauled its pricing in May 2026, retiring the old CMS and Business site plans and replacing them with a streamlined tier structure.

Webflow pricing operates on two separate billing layers: a Workspace plan (who can access and collaborate on sites) and a Site plan (what each individual published site can do). A single Webflow site with one editor on Basic costs $180/year — roughly 9x Carrd Pro Standard.

Workspace seats add cost on top: Full Seat at $39/month, Limited Seat at $15/month, and Free Seat at $0 for reviewers who can comment but not edit.

Webflow CMS vs. Framer CMS: Relational Content Depth

This is where the two platforms diverge most significantly for content-heavy sites. Consider a content schema with three related types: Authors, Articles, and Categories.

In Webflow, this schema is straightforward:

• "Articles" Collection with a Reference field linking to "Authors" and a Multi-Reference field linking to "Categories"
• Template pages for Articles automatically populate author name, bio, avatar, and all linked categories from the related Collections
• You can filter Collection Lists by referenced field values (e.g., "show only articles where Author = Jane Smith")

In Framer, as of mid-2026, the CMS supports basic Collections but does not natively support reference fields between Collections. To implement an author-article relationship, you must either duplicate author data in each article record (brittle, inconsistent) or use a custom code component with a hardcoded data map (requires developer time, breaks on content changes). For a site with 3 authors and 20 articles, this is manageable. For 50 authors and 500 articles, it's an ongoing maintenance problem.

If your content structure is flat — blog posts with title, body, date, and cover image — Framer's CMS is adequate. If it's relational, Webflow is the correct choice.

Trade-offs

The Webflow learning curve is steep relative to Carrd. Unlike Carrd's simplified container model, Webflow requires a working understanding of the CSS Box Model, Flexbox, and CSS Grid. You're acting as a frontend developer using a graphical interface. Budget 10–20 hours to reach productive proficiency if you've only used Carrd or similar simple builders.

Code export is a paid Workspace feature, not a Site plan feature. Exported code excludes CMS content, forms, site search, Memberships, and other platform-managed behavior. Exporting code does not mean exporting a portable, independently operable site.

Migration Path: Carrd → Webflow

1. Extract assets from Carrd manually (images, copy, embed codes). Use the Pro Plus code export as a reference.
2. Rebuild in Webflow's Designer — there is no automated Carrd importer.
3. Structure text content in CSV, map columns to Webflow CMS field types, and import via the CMS Import tool.
4. Repoint your custom domain DNS (A record and CNAME to Webflow's publishing endpoints).
5. Set up 301 redirects in Webflow's hosting settings. Webflow supports CSV import and export of redirect rules, which significantly reduces manual entry for sites with many anchor-to-page redirects.
6. Keep Carrd active for at least 48 hours during DNS propagation before canceling.

For a deeper comparison of CMS architectures, see Notion vs Webflow: Architecture, TCO & Migration Guide.

Framer: The Design-Velocity Route

Framer is the closest Carrd replacement if your current site is mostly hero blocks, feature sections, and fast design iteration. It has captured a significant share of the designer market from teams who find Webflow too rigid and Carrd too limited.

Architecture

Framer is built on React. Published sites are React applications deployed on Vercel's edge network with server-side rendering and automatic image optimization. The editor feels like Figma — free-form canvas design over strict CSS document flow. Framer includes a native CMS sufficient for standard blogs, changelogs, and content libraries with flat data structures.

Pricing (2026)

Editor seats cost $20/month on every plan. Framer introduced a $10/month Content Editor seat in mid-2026 that grants CMS-only access without full design permissions — useful for teams where a marketer needs to publish blog posts without touching layout.

One nuance teams miss: the free plan supports prototyping with generous editor limits, but publishing to a custom domain requires a paid plan. Framer's per-site billing model means running three published sites costs three separate plan subscriptions, not one account fee.

Trade-offs

CMS relational depth is limited. As detailed in the Webflow section above, Framer's CMS lacks native reference fields between Collections. Flat content structures work well; relational schemas require workarounds.

No HTML export. Framer does not offer HTML export for self-hosting. Published sites depend on platform-managed pre-rendering, image optimization, font subsetting, and SSR infrastructure. This is a strong hosted platform, but organizations that require source portability or self-hosted deployment cannot use Framer without a full rebuild.

Per-site billing compounds. At $10/month (Basic), one site costs $120/year. Two sites cost $240/year. Three cost $360/year — already approaching Carrd Pro Plus ($49/yr for 25 sites) in per-site economics.

Framer is the closest to Carrd's "build fast, ship fast" ethos — but at $120/yr (Basic) vs. $19/yr, the cost jump requires clear justification.

Migration Path: Carrd → Framer

The same manual process applies: copy content, rebuild in Framer's canvas editor, repoint DNS. No Carrd importer exists. The rebuild is often faster than Webflow because Framer's section-based canvas is conceptually closer to Carrd's structure. The most efficient path for design-led teams: recreate the layout in Figma → use the Figma-to-Framer plugin to import frames → wire up CMS fields for dynamic content.

Squarespace: All-in-One for Service Businesses

Best for: Small businesses and creators who need multi-page sites, blogging, appointment scheduling, and e-commerce without touching code or managing separate tools.

Pricing (2026)

Squarespace began rolling out a new four-plan pricing model in early 2026, replacing the old Personal, Business, and Commerce plan structure.

The Stripe Embed vs. Native Commerce Gap

Carrd users who have embedded Stripe Buy Buttons or Payment Links often underestimate how much commerce infrastructure they're missing. Squarespace's native commerce layer (Core and above) provides: a shopping cart that persists across products, subscription billing management, tax calculation by jurisdiction (no separate Stripe Tax fee), branded checkout at your domain rather than Stripe's hosted pages, inventory management, discount codes, abandoned cart recovery, and an order management dashboard. Each of these requires a separate integration or is simply unavailable in a Stripe-embed-only setup.

The 3% transaction fee on Squarespace Basic makes it less economical than Core for any site generating meaningful revenue. At $500/month in sales, Basic costs $15/month extra in transaction fees — the same as upgrading to Core. At $1,000/month, the math forces an upgrade.

Trade-offs

Price floor is high for simple sites. At $192/yr for Basic, Squarespace is 10x Carrd Pro Standard for what might still be a single-page portfolio.

Per-site billing. Each Squarespace site has its own billing plan. Managing 10 sites on Squarespace Basic costs $1,920/year. Managing 10 sites on Carrd Pro Standard costs $19/year. The economics only favor Squarespace when each site genuinely requires its feature set.

No free tier for published sites. Squarespace offers a 14-day free trial, but you must select a paid plan to publish with a custom domain.

Limited design flexibility. Templates are polished but rigid compared to Webflow or Framer. Custom CSS is supported, but deep layout changes require either template modifications or Squarespace's Developer Mode, which breaks the visual editor.

Squarespace makes sense when the site needs to act like a complete business surface — not just a landing page. Built-in blogging, appointment scheduling (Acuity Scheduling integration), e-commerce, and email marketing reduce the number of separate tools required.

Migration Path: Carrd → Squarespace

Manual rebuild in Squarespace's template editor. No import from Carrd. Squarespace supports 301 redirects natively via URL Mapping in the Not Found settings. Squarespace can import content from WordPress (via WXR file), Blogger, and Tumblr — but not from Carrd.

If your site is crossing into full storefront territory with inventory management, fulfillment, and multi-channel selling, Top Shopify Alternatives in 2026 is the more relevant comparison.

Notion + Super/Feather: The Content-First Route

If your Carrd site is primarily text-driven — documentation, wikis, resource directories, or changelog pages — a Notion-backed rendering layer is the lowest-friction migration path for teams already working in Notion.

Architecture

Platforms like Super and Feather act as caching and rendering layers on top of the Notion API. You manage all content in Notion databases. The builder fetches content from Notion's API, strips the heavy JavaScript payload from Notion's native renderer (which typically adds 1–3 MB of JavaScript to a page), applies custom CSS and branding, and serves static or cached HTML to visitors. The result is a site that feels and performs like a custom build while editing exclusively in Notion.

Pricing

• Notion Plus: $10/user/month (billed annually: $96/user/year)
• Super: $19/month per site (annual: ~$228/year)
• Feather: $14/month per site (annual: ~$168/year)
• Year 1 TCO (single editor, Notion Plus + Super): ~$324/year

Trade-offs

Design flexibility is rigidly constrained to Notion's block model. You cannot build overlapping layouts, complex scroll animations, or pixel-precise sections. What you can do is publish any Notion page or database as a navigable URL, apply a custom domain and brand stylesheet, and let your team edit content without ever leaving Notion.

This route works when content velocity matters more than visual differentiation. For teams already living in Notion, editorial friction drops to near zero — any teammate who can write a Notion page can publish to the site. No training on a new visual editor is required.

Typedream: The Low-Friction Step-Up

Typedream is the most direct feature-level upgrade for Carrd users who want multiple pages and a light CMS without taking on Webflow's complexity. Its editor resembles a Notion-style block editor rather than a canvas designer.

Pricing

Typedream offers a free plan and three paid tiers: Launch at $15/month, Grow at $30/month, and Pro at $49/month (annual billing). Launch includes unlimited pages, custom domain, SEO controls, code injection, analytics, one blog CMS collection, 1,000 form submissions per month, and 2 collaborators.

Typedream's CMS includes one-click Notion database connections for rendering Notion content inside Typedream pages — a useful bridge for teams that store content in Notion but want more design control than Super or Feather offer.

Trade-offs

Platform longevity risk. Typedream has shown limited public development activity and community engagement over the past year. For a site you plan to maintain and grow, building on a platform with uncertain roadmap and support continuity is a real risk. If Typedream were to discontinue or significantly change pricing, migrating off it would involve the same manual rebuild process you used to get there.

Pricing is misaligned with positioning. At $180/year for Launch, Typedream is in Webflow Basic territory ($180/year) with fewer features, a smaller ecosystem, and less proven infrastructure. The value proposition requires that you genuinely cannot learn Webflow — not just that you prefer not to.

Limited SEO depth. Basic meta title and description support, but no native structured data, no redirects manager at lower tiers, and limited analytics compared to Webflow or Squarespace.

Typedream is a reasonable bridge product for MVPs and personal sites. It is a risky choice for anything you plan to operate and grow for more than 12 months.

Self-Hosted (Astro / Hugo / Next.js): Developer Control

For engineering teams, a custom stack on Vercel, Netlify, or Cloudflare Pages delivers total control without vendor lock-in — and hosting costs that approach zero for low-traffic sites.

Astro is the current preferred framework for content-heavy sites due to its Island Architecture: components ship zero JavaScript to the client by default, with interactive islands opting into hydration only where needed. A 20-page Astro site with server-rendered Markdown content typically achieves Lighthouse Performance scores of 95–100 without optimization work, compared to a comparable Webflow site requiring manual lazy-load configuration to hit the same range.

Pair Astro with a headless CMS — Sanity (free tier: 10 users, 10 GB bandwidth, 2 datasets), Contentful (free tier: 5 users, 1 space, 25K records), or Markdown files in Git for small teams — to enable non-technical content editing without touching code.

# Deploy a single-page Astro site to Netlify
npm create astro@latest my-landing-page
cd my-landing-page
npx netlify deploy --prod

Pricing

• Hosting (Vercel/Netlify/Cloudflare Pages): Free on hobby tiers; $20/month for team tiers with higher bandwidth and build limits
• Headless CMS: Free tiers for Sanity and Contentful; production usage with multiple editors starts at $99/month for Contentful, $15/month for Sanity Growth
• Year 1 TCO: Essentially the engineering hours invested — subscription costs can be near zero for solo projects

Trade-offs

This route requires dedicated engineering to build and maintain. Marketers cannot edit site layout without developer help unless you invest in a visual editing layer (Storyblok, Sanity Studio, TinaCMS). The initial build time is significantly higher than any visual builder — a Carrd page takes 30 minutes, a comparable Astro page takes 2–4 hours for an experienced developer, longer for initial project setup.

This path only makes sense if you have engineering resources available, care about code ownership, and either have no non-technical collaborators or are willing to invest in a content editing layer.

TCO Comparison: Carrd vs. Alternatives (Year 1)

All prices assume annual billing, a single site with custom domain, and one editor. E-commerce transaction fees are not included unless they represent zero-cost options.

The cost jump from Carrd to any full-featured alternative is 6x–19x in subscription costs alone. Engineering time, migration labor, and seat costs push the real first-year figure higher.

Hidden Cost Multipliers

Seat and contributor pricing. Framer charges $20/month per additional editor. Squarespace Basic caps at 2 contributors. Webflow adds a separate Workspace billing layer — a team of 3 editors at Full Seat pricing adds $117/month to whatever Site plan you're on. These costs compound fast for agencies or small teams.

Commerce transaction fees. Squarespace Basic charges 3% on all store transactions. At $2,000/month in sales, that's $720/year in fees — more than the cost of upgrading to Core ($84/year more expensive). Evaluate the break-even point before choosing a plan.

Portability is a real cost center. Carrd code downloads require Pro Plus and break platform-dependent features. Webflow exports code but leaves CMS content, forms, site search, and Memberships behind. Framer does not support HTML export at all. Squarespace can export some content types (blog posts as WXR file) but cannot bulk-export images, videos, or page layouts. "Export" in none of these platforms means "fully portable." If you leave, you rebuild.

Migration labor is the hidden line item. The time sink is rarely rebuilding the hero section or the color scheme. It's recreating forms with equivalent validation and routing, implementing 301 redirects for every anchor link that became a real URL, migrating analytics configuration, rebuilding structured content, and verifying SEO settings across every page. Budget conservatively and test thoroughly before cutover.

Decision Framework: Which Alternative Fits

Stay on Carrd if:

• Your site is genuinely one page with no need for discrete URLs
• You don't need a blog, relational CMS, or native e-commerce
• Cost minimization outweighs feature depth — $19/year is hard to beat
• Basic page-level SEO (title, description, Open Graph) is sufficient for your goals

Move to Webflow if:

• You need CMS-driven content with relational fields (blog, documentation, portfolio with categories, author pages)
• Design precision at the CSS level matters and you'll invest in learning the tool (budget 10–20 hours)
• You want a platform with a large agency and freelancer ecosystem for future handoffs or outsourced development

Move to Framer if:

• You're a designer who wants motion, scroll interactions, and visual fidelity built into the builder
• Your content structure is flat (blog posts with title, body, date, image — no cross-collection references)
• You want faster setup than Webflow with comparable design quality

Move to Squarespace if:

• You need built-in e-commerce, blogging, appointment scheduling, and email marketing from a single platform
• You prefer polished templates over blank-canvas design
• Your site needs to function as a complete business surface, not just a landing page

Move to Notion + Super/Feather if:

• Your site is content-heavy (documentation, wikis, directories, resource pages)
• Your team already works in Notion and content velocity matters more than visual flexibility
• You want near-zero training cost for content contributors

Move to Typedream if:

• You want Carrd-like simplicity with multiple pages and a light CMS
• You're building an MVP or personal project and need a fast setup with low friction
• You consciously accept the platform longevity risk of a smaller vendor

Go self-hosted if:

• You have engineering resources available and want zero vendor lock-in
• You want sub-$20/year hosting with full code ownership
• Non-technical collaborators either don't need to edit the site or you're willing to invest in a CMS layer

Migrating Off Carrd Without Breaking SEO or Forms

The failure mode in Carrd migrations is almost never pixel-level design transfer. It's behavior loss: forms stop posting, old anchors die, analytics duplicate, or a single-page URL structure gets split into pages without a redirect plan.

The Hash Fragment Problem

In Carrd, your pricing section lives at yoursite.com/#pricing. Search engines do not index the #pricing fragment — they only index yoursite.com. When you move to Webflow or Framer, that section becomes a distinct page: yoursite.com/pricing.

You cannot set up a server-level 301 redirect for a # fragment. The hash never reaches the server. If external sites linked to yoursite.com/#contact, those links will resolve to your new homepage with no redirect. You must use client-side JavaScript on the new homepage to detect the hash and redirect:

// Redirect legacy Carrd anchor links to new discrete pages
if (window.location.hash) {
  const section = window.location.hash.replace('#', '');
  const validSections = ['pricing', 'contact', 'about', 'faq'];
  if (validSections.includes(section)) {
    window.location.replace('/' + section);
  }
}

This script runs on page load, checks for a known anchor hash, and issues a client-side redirect to the new URL path. Add this to your new homepage's <head> or custom code block. Maintain the validSections array to match every anchor you used in Carrd.

Note: client-side redirects are not equivalent to HTTP 301 redirects for SEO purposes. Because Carrd's #fragment URLs were never individually indexed by search engines (the hash never reaches the server and is excluded from Google's index), you are not losing ranked URLs — you're only preserving external link destinations. This is a UX concern more than an SEO one.

Migration Checklist

Regardless of your target platform, follow this sequence:

1. Audit the live site first. Inventory every section anchor, form destination, analytics tracker, widget, embed, image asset, custom CSS block, and meta setting. "It's just a simple page" is consistently wrong. Use browser developer tools to capture the full network request list on page load.

2. Export form submissions. Copy existing form data from Carrd's dashboard before canceling. Carrd form data is not included in the code export and will not transfer automatically to any new platform.

3. Download the code export (Pro Plus only). Even if you won't reuse the HTML, it's the most reliable reference for layout structure, image file names, and CSS variable values.

4. Map URLs before rebuilding. If /#pricing becomes /pricing, document the full redirect plan before writing a line of new code.

old_path,new_path,type,reason
/,/,200,home remains home
/#pricing,/pricing,client-side,section becomes standalone page
/#faq,/faq,client-side,section becomes standalone page
/#contact,/contact,client-side,keep lead form URL stable

5. Rebuild forms and integrations first, not last. Carrd Pro Plus can route form submissions to Stripe Checkout, Zapier, Make, n8n, and Airtable. On your new platform, recreate and test: spam controls (honeypot or CAPTCHA), hidden field mapping, conditional notification routing, thank-you page redirect, and webhook delivery. Test before cutover, not after.

6. Repoint DNS after validation. Update A record and CNAME to the new host's published endpoints. Only switch DNS after verifying redirects, metadata, analytics firing, and form submission handling on the new platform. Allow 24–48 hours for full propagation.

7. Submit a new sitemap. Your new platform will generate a comprehensive XML sitemap containing all discrete URLs. Submit to Google Search Console immediately after DNS propagation to accelerate recrawling. Carrd's single-page structure had one URL; your new site may have 10 or 100. Google needs the sitemap to discover them.

8. Update external links. Social media profiles, email signatures, Google Business Profile, directory listings, press mentions, podcast show notes — everywhere your Carrd URL appears needs updating. The client-side hash redirect handles existing backlinks, but your own controlled properties should point to canonical new URLs.

9. Keep Carrd active during transition. Do not cancel your Carrd subscription until DNS has fully propagated and the new site is confirmed live and functional. The $19/year cost is trivial compared to a gap in site availability.

10. Verify post-migration. Check Google Search Console for crawl errors 48–72 hours after DNS propagation. Test every form submission end-to-end. Confirm analytics events are firing without duplication. Spot-check Open Graph tags on social sharing previews.

When Staying on Carrd Is the Right Call

Do not migrate simply because you want a different visual aesthetic or a trendier builder. Carrd Pro Standard at $19/yr gives you custom domains, forms, embeds, analytics, and meta tags. Pro Plus at $49/yr adds advanced forms (with Stripe, Zapier, Make, n8n, and Airtable integrations), site downloads, redirects, password protection, and canonical URL control.

The rational case for migration is mathematical: does the revenue or capability enabled by multi-page SEO, structured CMS content, better commerce infrastructure, or team collaboration justify a 6x–19x increase in annual subscription cost plus the engineering time of migration?

If you have a single landing page generating leads, $19/year on Carrd is probably the correct answer until that page outgrows its URL.

If you're an agency managing dozens of Carrd micro-sites, the manual extraction and CMS remapping work becomes the primary cost — not the platform subscriptions. That's the scenario where systematic DOM extraction, structured JSON output, and automated CMS import tooling are required to maintain margins during replatforming at scale.