SOLID GenKentico migration
Your Kentico 13 site moves to Xperience by Kentico with its content, URLs and search ranking intact.
How we work
- We audit before we promise: content, custom code, integrations and traffic.
- We keep every URL that earns traffic and map the rest with redirects.
- We port code in small slices, each one reviewed and tested before the next.
Skills we have
- Xperience by Kentico
- .NET
- C#
- SQL Server
- Azure
How an engagement runs
Durations are ranges for a mid-size project. We confirm them with you before we start.
Discovery and audit 1 to 2 weeks
An audit of content types, custom modules, integrations and URLs, with the risks ranked.
We need: Read access to the current site, its code repository and analytics.
Migration plan and estimate About 1 week
A written plan with scope, phases and a cutover approach. The estimate follows the audit and is agreed with you before any contract.
We need: A decision on what to keep, drop or rebuild, and a named decision maker.
Content model and architecture 2 to 3 weeks
A content model and solution structure for Xperience by Kentico, agreed before code moves.
We need: Time with your editors to confirm how they work with content today.
Migration and code port 6 to 10 weeks
Content, media and code moved in slices, with a working staging site to review each one.
We need: A reviewer who answers questions within a working day, and a staging environment.
QA and UAT 2 to 3 weeks
A tested site, a defect list worked down to zero, and a redirect and SEO check.
We need: Your testers, with a short list of the journeys that matter most.
Go-live and hypercare 1 week, then 2 to 4 weeks of hypercare
A rehearsed cutover, a rollback plan, and close monitoring after launch.
We need: A launch window agreed with your team and access to DNS.
Are you ready to migrate?
Eight questions about your current Kentico site. Your answers stay in your browser until you choose to email them to us.
Answer all eight questions to see where you stand.
Questions
How long does a migration take?
For a mid-size site, expect roughly three to five months from audit to launch. The audit gives you a firmer date.
Will we lose search ranking?
We keep URLs that earn traffic, redirect the rest and check both before and after launch.
Can editors keep working during the migration?
Yes. We plan a content freeze only for the final cutover, and keep it short.
Do you migrate custom modules?
We review each one in the audit and decide with you whether to port, replace or retire it.
Tell us what you’re building.
A 30-minute call. We listen, ask the awkward questions, and tell you honestly if we’re the right team.