Introduction
Once we understood why we were migrating, the next challenge was how.
At Techxot, we have successfully done 30+ Umbraco migration from legacy versions to the latest version and Umbraco Cloud. When you choose Techxot as an Umbraco development services partner, we prioritize aligning your business goals and implementation outcomes. We keep our Umbraco migrations systematic, efficient, and safe, without compromising on timelines or data integrity. We are a team of deep expertise who work closely with you on approaches for cloud migration.
Quick recap in Umbraco migration approach
Before we start let’s have a quick recap of the project and challenges as to why this Umbraco migration was initiated:
Limited legacy framework features
End of support for long standing Umbraco v8
Legacy version upgrade complexity and security risks
Migration could risk business downtime
After understanding the core challenges for migration, we recommended complete rebuilding, started with setting up a fresh v13 LTS foundation, adopted modern .NET 8, replaced unsupported packages, content and media migration was carefully phased, and recommended continuous testing. A cloud migration approach initiated this process with planning, environment setup, and tool selection, laying out the foundation for everything that followed.
1.Planning the Migration According to Time Constraints
Our client had a clear goal to migrate and go live within a fixed time frame.
We started by creating a Umbraco migration roadmap, splitting the work into 4 main phases:
1. Environment setup
2. Content and schema migration
3. Testing and validation
4. Cloud deployment
Each phase had defined checkpoints and buffers for unknowns, ensuring we caught issues early rather than post-deployment. We strategically prioritized platform stability, scoped features, and clearly identified the fixed and flexible timelines.
2.Setting Up the Umbraco v8 Project Locally
We cloned the existing Umbraco v8 repository and configured it locally to analyze:
Existing document types, data types, and templates
Custom controllers and services
Media structure and folder paths
Flagged legacy components for action
Installed packages and dependencies
3.Setting Up the New Umbraco Cloud v13 Project
We then created a fresh Umbraco Cloud v13 LTS instance which is .NET 8 (.NET Core). The cloud migration approach was embedded with an idea to start cleaning and bring in only what was essential.
Steps included:
Setting up connection strings in appsettings.json
Verifying database connectivity
Installing essential extensions (uSync, Deploy)
Setting up Git for version control
This setup served as our target environment for all migrations and testing.
4.Using uSync for Migration and Content Transfer
uSync became the backbone of our migration workflow.
Here’s how we used it:
Installed uSync migration packer in the v8 project
Exported document types, data types, templates, and content
Imported them into the new v13 instance
Verified that all nodes and schema synced correctlyuSync saved us days of manual recreation, especially for large content structures.
5.Identifying Legacy Data and Dependencies
Next, we audited all custom data types, code, and external dependencies.
Some of them:
Relied on obsolete property editors
Integrated with external systems using outdated SDKs
We listed all of these and marked which could be upgraded, replaced, or rewritten.
6. Package Compatibility and Alternatives
Not every v8 package works in v13 (especially those not updated to .NET Core).
We created a compatibility matrix, identifying:
Safe to migrate
Requires update
Deprecated (like legacy Redirects, old Media Picker)
This step helped us avoid surprises later when content failed to render due to unsupported property editors.
7.Handling Database Changes (NodeID Differences)
Umbraco v13 handles NodeIDs and GUIDs differently from v8.
To prevent mismatches, we:
Verified all content relationships (especially in Nested/Block content)
Checked for orphaned nodes
Ensured all media items had consistent GUID references
It was tedious but skipping this can easily lead to broken links or 404s post-migration.
8.Planning Data transfer Without Data loss
Our final planning step focused on content integrity:
Media files were synced manually and verified post-import
JSON properties were tested for schema compatibility
Backup checkpoints were set between each importThis allowed us to roll back easily in case of conflicts or corruption.
Key Challenges Overcome with Cloud Migration Approach
Made third-party package compatible
Content and media disruptions avoided
Implemented must have features over nice to have ones
Umbraco APIs reliance was avoided
Conclusion
We carefully planned the approaches in cloud migration because it ensured platform performance, stability, smooth transitions, and business scalability with zero to minimal downtime. By the time we finished this phase, we had:
Umbraco v13 fully running
A clean migration plan
Backup and rollback strategies
Verified compatibility reports for packages and content
This preparation turned a risky upgrade into predictable, controlled migration.
With our expertise and business first approach in complex Umbraco migration with multiple brands over the years, we don’t just upgrade but future proof your digital platforms by proposing migration frameworks for long-term business stability.
Techxot has successfully delivered 3 migration last month with zero disruption and maximum value. Choosing Techxot as your Umbraco migration partner plan your strategic and seamless Umbraco cloud migration to improve performance, stability, growth and future readiness. Get in touch with us and plan your Umbraco migration today.
In Part 3, we’ll get into the real work – Core Migration between Umbraco v8 and v13 Migrating Content.
Core Migration: from uSync import to JSON fixes, media migration, and template restructuring.
