Published content
Content IDs, names, content-type aliases, hierarchy, routes, dates, cultures, and accessible property values.
Available migration objects and capabilities depend on the selected source and target systems. Check current integration status before using this planning guide.
What the migration covers
Umbraco is beta and source-only in the capability catalog. The current source path centers on the v2 Content Delivery API for published content, with optional least-privilege Management API access reviewed only for approved backoffice gaps.
Structured properties
Rich text, links, pickers, Block List, Block Grid, Nested Content, compositions, and custom-editor values after profiling.
Media and references
Media-library records, originals, picker relationships, metadata, alt text, inline references, and destination assets.
Variants and routing
Culture variants, translated routes, publication state, redirects, metadata, source URLs, and destination mapping.
What requires separate scope
Members, passwords, groups, protected-content behavior, Razor views, templates, macros, controllers, packages, workflows, forms, search indexes, relations, custom applications, and .NET integrations require separate security, data, or redevelopment scope.
Use the Delivery and Management APIs deliberately
Published delivery content and backoffice configuration have different permissions and risk profiles.
Start with Delivery API
Read approved published JSON, routes, hierarchy, cultures, properties, and expanded references through the least-privilege source.
Enable preview only if required
Use an API key for draft or protected Delivery API access only when those records are explicitly in scope.
Limit Management access
Request OAuth credentials only for required content types, media, users, members, redirects, or unpublished-data gaps.
Keep member data separate
Treat member identity, passwords, groups, protected routes, and authentication as a distinct security workstream.
Map by document type and property editor
Similar labels can hide different JSON shapes, so migration rules are organized by aliases, editors, and sampled values.
Inventory document types
Capture aliases, compositions, properties, data types, allowed children, variations, cultures, and record counts.
Profile complex values
Sample rich text, links, content/media pickers, blocks, grids, nested content, repeaters, and every custom editor.
Prepare destination structures
Approve content types, fields, blocks, taxonomies, media, relationships, languages, and fallbacks before loading.
Load dependencies in order
Create taxonomy, media, reusable elements, authors, and referenced records before dependent nodes resolve their IDs.
Validate rendered content, variants, and routes
Correct JSON counts are insufficient when property transformations determine what visitors and editors actually see.
Reconcile by content type
Compare source, extracted, transformed, loaded, skipped, failed, published, draft, culture, and accepted totals.
Inspect complex nodes
Review blocks, grids, pickers, compositions, media, links, variants, dates, custom-editor fallbacks, and destination rendering.
Crawl every route family
Test source and translated routes, redirects, canonicals, metadata, sitemap entries, internal links, and media URLs.
Confirm repeatability
Verify source-to-target IDs, dependency resolution, reruns, documented exceptions, cutover checks, and monitoring ownership.
How the workflow works
- 1. Discover: Confirm Umbraco version, Delivery API, optional Management API needs, document types, properties, cultures, media, members, routes, and destination readiness.
- 2. Map: Approve destination types, property transformations, blocks, references, assets, languages, URLs, rebuild work, and exclusions.
- 3. Dry run: Transfer representative document types and complex property values into staging and correct systematic mapping rules.
- 4. Validate: Reconcile records and inspect blocks, media, cultures, paths, metadata, rendering, relationships, and exceptions.
- 5. Cut over: Execute the approved final or delta plan, implement redirects, and complete culture-aware launch checks.
Technical references
Scope is reviewed against the source and destination documentation available for the project.