Kentico to Carrd Migration

Q: What do I do with my Kentico user accounts and roles when moving to Carrd?

Carrd has no user management system, no roles model, and no backend to store identity data, so neither Kentico Users nor Roles can land in Carrd. User records should be migrated to a dedicated identity or CRM platform (such as Auth0, Firebase Authentication, or HubSpot), and Kentico passwords cannot be exported regardless of destination, so all users will need to reset credentials on whatever system they move to. If the Carrd site requires login or gated content, a third-party tool like Memberspace or Outseta must be bolted on externally; those user records would live in that service, not in Carrd.

Q: How do I preserve my Kentico URL redirects and aliases after switching to Carrd?

Carrd has no routing layer and no support for URL redirect rules, so Kentico URL Redirects and Aliases cannot be migrated into it directly. The redirect logic must be re-implemented at an infrastructure layer that sits in front of the Carrd site: for example, Cloudflare Page Rules, a Netlify _redirects file, or Vercel rewrites. Export the full redirect inventory from Kentico first and keep it in a mapping document, because once the Kentico instance is decommissioned that data is gone and every redirect will need to be manually re-entered in whichever infrastructure layer you choose.

Q: My Kentico site has multiple languages. What happens to that content on Carrd?

Carrd has no localization system, no culture-code configuration, and no multi-language content model, so Kentico's Languages entity and all language variants of your content have no destination in Carrd. If serving content in multiple languages is a hard requirement, Carrd is not a suitable target and an alternative platform such as Webflow, WordPress, or Squarespace should be evaluated instead. The only partial workaround (building separate Carrd sites per language and routing visitors with Cloudflare Workers) is a re-architecture project, not a data migration, and means manually rebuilding every language version in Carrd's visual editor.

Q: Does it matter which version of Kentico I'm running before starting this migration?

Version matters for how your content can be extracted from Kentico, even though the Carrd side has no API at all. Kentico Xperience 13 and later expose a Management API suitable for bulk extraction, while Kentico 12 and earlier rely on the .NET CMS.DataEngine and have no comparable REST surface, requiring direct database access for structured exports. Kentico's own Migration Toolkit (if you are using it for any parallel work) requires the source instance to be on version 13.0.64 (Refresh 5) or newer, and it does not move page type inheritance, field categories, ACLs, or user passwords regardless. Kentico Xperience 13 reaches end of support on 31 December 2026, so teams still on older versions are already running unsupported software, which adds urgency to scoping any export work promptly.

Q: Do I need professional help for this migration?

Yes. Professional help ensures proper field mapping and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Q: Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Q: Will the migration set off automations or send emails or notifications to customers, our team or anyone else?

No. Before the sample or full migration starts, we confirm with you that nothing in Carrd will send messages about the migrated data: we import with notifications switched off wherever Carrd allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.

Q: Can you migrate data that Carrd can't take in through an API?

In many cases, yes. Where something can't be written through an API, we recreate it through Carrd's user interface where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.

Q: How long does the Kentico to Carrd migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity; very large migrations, such as several hundred thousand records, take longer. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Q: Will there be downtime when migrating from Kentico to Carrd?

No. Our migration process is designed for zero downtime. Kentico stays fully operational throughout: the bulk migration runs in the background and the cutover is fast, so there is no disruption to your live business operations.

What Our Customers Say

Real migration stories

Direct Review

“They were SO helpful. We had a few hiccups because our migration was in the middle of the process, but they were really flexible and did multiple delta migrations for us. We were able to map a lot of our old ticket data so it's usable for comparisons in the future.”

Direct Review

“Overall a great experience. We had to go back a few times to get everything just right, which was totally expected. The transition was smooth, and there was no data loss.”

Direct Review

“One of the easiest migrations I've ever been through. The team took care of everything — all our data, customer interactions and macros. The process was clear, straightforward and we felt supported all the way. An absolutely seamless experience for our support team and our customers.”

Direct Review

“Fantastic at both guiding us through the process and helping us fix things as they come up and dial them in.”

Reviewed on G2

“The ease of the process and that ClonePartner was informing me what was going on at every step. If you're on the fence, do it. ClonePartner are great!”

See all customer stories →

CUSTOM MIGRATION

Fully customizable engineer-led migration

Tailor your migration from Kentico to Carrd exactly to your needs with our flexible customization options. Our experts will configure the perfect migration plan for your business.

Migration Filters

Data Types

MIGRATION TIMELINE

Your Kentico to Carrd migration, step by step

See how long your migration will take from start to finish. Drag the slider to estimate based on your data volume.

How many records are you migrating?

<10K 50K 100K 250K 500K 1M 2M 5M 10M+

Checklist ~3 days

Sample 1 day

Review ~2 days

Full 2 days

Delta 1 day

Your team ClonePartner

Estimated total

~9 business days

Migration Checklist

1 day · ClonePartner ~2 days · Your team

We prepare the optimal data mapping as a shareable spreadsheet. Your team reviews, approves, and adds any customizations.

Sample Migration

1 day · ClonePartner

We run a test migration with a representative sample of your data to verify mapping accuracy and identify any potential issues before the full run.

Review & Approve

~2 days · Your team

Your team reviews the sample migration results, confirms data accuracy and mapping, and gives the go-ahead for the full migration.

Full Migration

2 days · ClonePartner

We execute the complete migration of all your data to your new Carrd, with real-time progress tracking and comprehensive logging.

Delta Migration

1 day · ClonePartner

We capture and transfer any new data that was added or updated during the main migration to ensure no data is lost. This final sync keeps everything current.

Pros and cons of different migration options

Choosing the right approach is key because migrating from Kentico to Carrd isn't just about moving data – it's about protecting your content, SEO, and reader experience.

Feature / Criteria	ClonePartner	Automated Tools	CSV Import	In-house migration
Custom Scripting for complex data	✓ Engineers build & maintain	✗ No	⚠ Manual	✓ Yes – but costly
Sandbox & Pilot Migrations	✓ Full sandbox + pilot plans	⚠ Limited	✗ No	⚠ Often Informal
Manual validation & reconciliation	✓ Automated + manual QA	✗ No	✓ Yes (Manual)	✓ Heavy manual effort
Backup & rollback plan	✓ Robust procedures	✗ No	✗ No	⚠ Often incomplete
Handles automation and integrations	✓ Full support	⚠ Partial	✗ No	⚠ Possible but fragmented
Post-migration engineer support	✓ Dedicated engineers	✗ No	✗ No	⚠ Limited support
Adaptable to API changes	✓ Proactive adaptation	✗ No	⚠ Manual fixes	⚠ Slower response
Turnaround / timeline predictability	✓ Predictable timelines	⚠ Fast but brittle	⚠ Slow and manual	⚠ Often slower
Data Security & Compliance	✓ High – enterprise grade	⚠ Medium (depends)	⚠ Low (manual)	⚠ Hidden gaps common
Pricing predictability	✓ Transparent & fixed	⚠ Low (per-job)	⚠ Low (manual hours)	⚠ High/variable OPEX
End-to-end project management	✓ Full E2E delivery & PM	✗ No	✗ No	⚠ Often partial
Business impact & opportunity cost	✓ No diversion of staff	✗ No	✗ No	⚠ Diverts engineering

What does an Engineer-led migration mean anyway?

Speed & Accuracy: Our Blended Method

We blend automation (smart scripts, bulk APIs) with human expertise for speed without risk. Our engineers manually check every mapping, validation, and exception.

You get:

Speed of automation for bulk record migration
Precision of engineers verifying integrity and business logic
Pilot migrations and sandbox testing to catch issues early
Real-time validation reports and rollback readiness

Result: 50x faster migrations than manual imports — with near-zero error rates.

Handling the Tricky Tech and API Details

The Kentico and Carrd APIs each behave differently, which is where our engineers shine. We build custom logic to handle the data quirks where generic tools typically break.

We handcraft API logic for:

Field mapping and transformation
Pagination, rate-limit handling, and throttling
Preserving content relationships, media, and revision history
Syncing custom fields, taxonomies, and templates without breaking structure

Our scripts: Natively retry failed calls, re-queue large attachments, and ensure data parity.

No Guesswork

We don't just promise smooth migrations—we measure and prove them. Every client receives a Migration Validation Report with all metrics.

Typical results across projects:

100% record-count parity between your Kentico data and Carrd
Zero downtime during staged cutovers
99.9% attachment integrity (verified via checksum)
Full automation and preservation of all business rules

Our standard: Includes full SEO and redirect preservation and 30 days of engineer-assigned support post go-live.

We Adapt to Your Setup (Not the Other Way Around)

No two teams configure Kentico or Carrd exactly the same way—with unique content models and data. We customize every migration script to fit your exact workflow, taxonomies, and templates.

Our engineers adapt for:

Custom fields, content types, and workflows
Multi-site or multi-language setups
Historical imports and partial (date-based) migrations
Integration re-mapping for search, analytics, or forms tools

The promise: If your data doesn't fit a standard template, we build one just for you.

Enterprise-Grade Security & Compliance

Your customer data is precious. Our migration process maintains the highest standards of security and regulatory compliance.

SOC 2 Type II

Independently audited compliance with rigorous security standards

ISO 27001

Certified information security management system

GDPR

Full compliance with EU data protection regulations

HIPAA

Certified for handling protected health information

AES-256 Encryption

Bank-grade encryption for all stored credentials

Latest TLS

Secure transfer protocol for all data in transit

Role-Based Access

We follow role-based access control for every migration project

Scheduled Deletion

Automatic data purging after migration completion

FAQ

Frequently Asked Questions

Everything you need to know about migrating from Kentico to Carrd. Can't find what you're looking for? Talk to our team.

Kentico → Carrd 4 Before you start 2 Data & mapping 2 Timeline & downtime 2 Security & access 1 Pricing 1 After go-live 2

Still have questions?

Book a free 30-minute consultation with our team.

Contact our team

Kentico → Carrd

4 questions

What do I do with my Kentico user accounts and roles when moving to Carrd?

Carrd has no user management system, no roles model, and no backend to store identity data, so neither Kentico Users nor Roles can land in Carrd. User records should be migrated to a dedicated identity or CRM platform (such as Auth0, Firebase Authentication, or HubSpot), and Kentico passwords cannot be exported regardless of destination, so all users will need to reset credentials on whatever system they move to. If the Carrd site requires login or gated content, a third-party tool like Memberspace or Outseta must be bolted on externally; those user records would live in that service, not in Carrd.

How do I preserve my Kentico URL redirects and aliases after switching to Carrd?

Carrd has no routing layer and no support for URL redirect rules, so Kentico URL Redirects and Aliases cannot be migrated into it directly. The redirect logic must be re-implemented at an infrastructure layer that sits in front of the Carrd site: for example, Cloudflare Page Rules, a Netlify _redirects file, or Vercel rewrites. Export the full redirect inventory from Kentico first and keep it in a mapping document, because once the Kentico instance is decommissioned that data is gone and every redirect will need to be manually re-entered in whichever infrastructure layer you choose.

My Kentico site has multiple languages. What happens to that content on Carrd?

Carrd has no localization system, no culture-code configuration, and no multi-language content model, so Kentico's Languages entity and all language variants of your content have no destination in Carrd. If serving content in multiple languages is a hard requirement, Carrd is not a suitable target and an alternative platform such as Webflow, WordPress, or Squarespace should be evaluated instead. The only partial workaround (building separate Carrd sites per language and routing visitors with Cloudflare Workers) is a re-architecture project, not a data migration, and means manually rebuilding every language version in Carrd's visual editor.

Does it matter which version of Kentico I'm running before starting this migration?

Version matters for how your content can be extracted from Kentico, even though the Carrd side has no API at all. Kentico Xperience 13 and later expose a Management API suitable for bulk extraction, while Kentico 12 and earlier rely on the .NET CMS.DataEngine and have no comparable REST surface, requiring direct database access for structured exports. Kentico's own Migration Toolkit (if you are using it for any parallel work) requires the source instance to be on version 13.0.64 (Refresh 5) or newer, and it does not move page type inheritance, field categories, ACLs, or user passwords regardless. Kentico Xperience 13 reaches end of support on 31 December 2026, so teams still on older versions are already running unsupported software, which adds urgency to scoping any export work promptly.

Before you start

2 questions

Do I need professional help for this migration?

Yes. Professional help ensures proper field mapping and preservation of relationships between records. Our engineer-led approach catches edge cases that automated tools miss.

Does ClonePartner provide guidance before committing?

Yes. We provide a free consultation and assessment. We'll review your data structure, discuss your requirements, and provide a detailed migration plan and fixed-price quote before you commit to anything.

Data & mapping

2 questions

Will the migration set off automations or send emails or notifications to customers, our team or anyone else?

No. Before the sample or full migration starts, we confirm with you that nothing in Carrd will send messages about the migrated data: we import with notifications switched off wherever Carrd allows it, and either pause any automation that could send them for the migration window or give it a condition, such as a suppression tag, that skips migrated records, which lets your live automations keep running for new records. We only proceed once you have confirmed it. If you want anyone told about the move, that message is sent separately, once the migrated data has been checked.

Can you migrate data that Carrd can't take in through an API?

In many cases, yes. Where something can't be written through an API, we recreate it through Carrd's user interface where the interface allows it, and where that work is repetitive we script and automate it. We tell you up front which items are handled this way, because recreating them through the interface can add time to the schedule.

Timeline & downtime

2 questions

How long does the Kentico to Carrd migration take?

Most migrations complete within 1–5 business days, depending on data volume and complexity; very large migrations, such as several hundred thousand records, take longer. We provide a detailed timeline after the initial assessment and can often complete small migrations in under 24 hours.

Will there be downtime when migrating from Kentico to Carrd?

No. Our migration process is designed for zero downtime. Kentico stays fully operational throughout: the bulk migration runs in the background and the cutover is fast, so there is no disruption to your live business operations.

Security & access

1 question

Can we whitelist a single IP instead of opening our network to your migration tool?

Yes. All migration traffic runs through a centralized system using one fixed IP, which your IT team can whitelist instead of opening broader network access.

Pricing

1 question

Is migration pricing a flat fee, or does it scale with data volume?

It's a flat fee with no hidden costs. The price we agree with you for your scope is the price you pay, and small variances in the final volume, a bit more or less, are included.

After go-live

2 questions

What support do you provide after the migration goes live?

At ClonePartner, we consider ourselves your partners in this journey. We take full accountability for your migration's success. Once your migration goes live, we provide 30 days of comprehensive post-migration support as standard, and longer support, such as 60 or 90 days, can be agreed for your project. During this period, we help with anything related to your migrated data, so your migration is a complete success.

After migration, do I contact ClonePartner or the platform's own support if something looks wrong?

ClonePartner is the contact for anything about the migrated data itself. Questions about the platform itself, such as how its features and settings work, go to the platform's own support or to whoever administers it for you.

Migrate from Kentico to Carrd with precision & ease

Intelligent Human-Verified Data Mapping

Real migration stories

Fully customizable engineer-led migration

Your timeline. Our engineers.

Your Kentico to Carrd migration, step by step

Pros and cons of different migration options