Ways to connect Umbraco
Reloque only ever reads from the source, and connects with what your Umbraco version allows.
API user
An API user's client ID and secret, with access to content, media and, if you move them, members.
Delivery API
Switched on in appsettings.json with an API key. Drafts are read through preview.
Bridge template
A read-only template pasted into Settings › Templates. Umbraco compiles it as it runs, so there is nothing to deploy or restart.
Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against). The Connect form finds the version at your address and offers the right way in, with a setup guide to download.
Umbraco 8 editors, written into Umbraco 17
| Umbraco | becomes | Umbraco |
|---|---|---|
| Nested Content | Block List | |
| Grid layout | Rich text, with its blocks | |
| Media Picker (ids) | Media Picker, re-picked by key | |
| Content Picker | Document Picker, to the migrated page | |
| Contentment Content Blocks | Blocks | |
| Image Cropper | Image Cropper, file and crops uploaded | |
| Members | Members, without passwords |
Umbraco migration routes
Reloque moves Umbraco content in both directions, and between two Umbraco sites. Reloque reads documents, media and each editor's values through the Management API (15 and later), the Delivery API (12 to 14) or the bridge template (7 to 13). SEO properties, such as seoTitle, metaDescription and noIndex, are read as the page's SEO data too, so they reach the other CMS's SEO fields, and Umbraco's own redirects from renamed and moved pages come with them (15 and later, or the bridge). Each route is mapped, previewed on the destination and checked by reading every record back.
Umbraco to WordPress
Posts follow the site's permalink setting, and with the Redirection plugin installed each old address redirects to its new one, along with the old site's own redirects. Media lands in the Media Library with its alt text, featured images, categories and tags are linked, with categories under their parents, and authors are matched to existing users. Every category and tag comes over, including those no post uses, and so does every term of your own taxonomies. Members can move too, as subscribers, without their passwords. The site's title, tagline, logo and timezone are set where the new site has none yet. Menus arrive as WordPress menus, at the theme location they had, with each link pointed at the moved page. Comments arrive with their replies, under each commenter's own name and email, at their own dates, approved or waiting for a moderator as they were. SEO data goes to Yoast SEO or Rank Math, whichever the new site runs, its social images copied to the Media Library. The WordPress guide covers the other side. Umbraco to WordPress, step by step.
Umbraco to Contentful
Records go into the space's own content types, matched by name, or into Blog post and Page types Reloque adds when the space has none and your role allows it. Bodies become Rich Text, with images uploaded as assets and links between records as links between entries. Categories, tags and authors become entries of the types the space links to, or Contentful tags. Each language goes into the locale of the same language, in the fields that are localized. SEO data goes into the type's SEO fields or an SEO entry, menus into menu and menu item entries and redirects into redirect entries, with types added for them where the space has none. Published records are published. The Contentful guide covers the other side. Umbraco to Contentful, step by step.
Umbraco to Sanity
Records go into the dataset's own document types, matched by name, writing the fields their documents have. A dataset with no posts or pages gets documents shaped as Sanity's blog starter (post, page, category, tag and author), which the Studio shows once its schema has those types. Bodies become Portable Text, with images uploaded as assets and links between records as references. Categories, tags and authors become documents of the types the dataset refers to. Each language becomes a document of its own, tied to the others as document internationalisation does. SEO data goes into an SEO object, menus into navigation documents and redirects into redirect documents. Drafts stay drafts, and published records are published. The Sanity guide covers the other side. Umbraco to Sanity, step by step.
Umbraco to Webflow
Records go into the site's own collections, matched by name, or into the collections of Webflow's blog template, which Reloque adds when the site has none: Blog Posts, Pages, Categories, Tags and Authors. Bodies stay rich text, with images uploaded as assets and links between records pointing at the new items. Categories, tags and authors become items of their collections, and SEO data goes into the collection's SEO fields. Published records are published, and drafts stay drafts. The Webflow guide covers the other side. Umbraco to Webflow, step by step.
Umbraco to Payload
Bodies become Payload rich text, images are uploaded to your upload collection, and categories, tags and authors are created where missing and linked, categories under their parents where your categories have a parent field. Blocks, arrays and groups are filled field by field, and relationships point at the migrated records. Each record keeps its old address in sourceUrl, for redirects, and with the redirects plugin installed each old address redirects to its new one, along with the old site's own redirects. A site in several languages moves into each locale of your localized fields. Members can move too, into a collection with sign-in other than your admins', without their passwords. Menus from another CMS fill a global's list of links, a main menu the header's and a footer the footer's. The Payload guide covers the other side. Umbraco to Payload, step by step.
Umbraco to Strapi
Bodies are written as Strapi blocks or Markdown, whichever each field is, images go to the Media Library, and cover images, categories, tags and authors are linked, categories under their parents where they have a parent relation. Strapi 5 sets its own publish date, so the original goes into a date field of your own. A site in several languages moves into each locale of a translated type. Members can move too, as Users & Permissions users in the role of their group, without their passwords. With a Redirect type of your own (from and to fields), each old address redirects to its new one; with strapi-plugin-redirects, the handover package has a file to import in its admin page. Menus from another CMS fill a single type's list of links, a main menu the header's and a footer the footer's. The Strapi guide covers the other side. Umbraco to Strapi, step by step.
Umbraco to Ghost
Bodies are sent as HTML, which Ghost turns into its own editor format. Categories become tags, posts keep their slugs at /<slug>/, and the redirects are added to Ghost's own when you connect with a staff access token (Ghost 5 and later); otherwise the handover package includes a redirects.yaml ready to upload. Comments arrive on their posts at their own dates, each by the member with the commenter's email: you choose on the Map step whether to add a free member for each commenter who is not one, signed up to no newsletter and sent no email. The Ghost guide covers the other side. Umbraco to Ghost, step by step.
Umbraco to Drupal
Each post and page becomes a node at its old address, as an article, a basic page or the content type you choose, with its fields in each field type's format. Categories and tags go into their vocabularies, nested where they were, images into the Media Library, and authors are matched to the site's users. SEO data from another CMS goes into Metatag's field, with sharing images copied. Menus are added to Main navigation, Footer or a menu of the same name, as JSON:API cannot create menus. Comments arrive with their replies, each by the site's user with the commenter's email or as a visitor. Members become users with no password, who set their own with Drupal's password reset page, and get a role only where it cannot edit the site. JSON:API cannot create Paragraphs, so blocks from another CMS are added to the body. A site in several languages comes in its default language, or each language as a node of its own, as JSON:API cannot add a translation; you choose on the Map step. With the Redirect module installed, each page's old address redirects to its new one, and the old site's own redirects come too. Drupal's JSON:API cannot change site settings, so the run report lists the site name, slogan and time zone to set in Drupal's admin. The Drupal guide covers the other side. Umbraco to Drupal, step by step.
Umbraco to Storyblok
Records go into the space's own content types, matched by name, or into Article and Page types Reloque adds, with categories and authors, when the space has none and your role allows it. Posts go into the folder their type's stories are in, or a Blog folder, and pages to the root. Bodies become rich text, with images uploaded as assets and links between records as links between stories. Categories and authors become stories in folders of their own, and tags Storyblok's own tags. Each language goes into the space's language of the same code, in the fields that are translatable. SEO data goes into the type's SEO fields, menus into a config story's navigation and redirects into redirect stories. Drafts stay drafts, and published records are published. The Storyblok guide covers the other side. Umbraco to Storyblok, step by step.
Umbraco to Umbraco
This is how an old Umbraco site reaches a current version: Nested Content becomes a Block List, the Grid becomes rich text, pickers are picked again on the new site, and members can move too, without their passwords. Umbraco to Umbraco, step by step.
Moving to Umbraco
Moving to Umbraco means defining document types before importing content. Think about the tree structure and language variants early.
WordPress to Umbraco
Reloque reads posts, pages, your own post types, media, categories, tags, your own taxonomies, authors, menus, comments, SEO data, the Redirection plugin's redirects and custom fields through the REST API, an export file or the bridge file. The REST API shows only the fields a plugin registers, such as ACF's; the export file and the bridge read every one. SEO data comes from Yoast SEO or Rank Math: the SEO title and description you set, the focus keyword, the canonical address, noindex and nofollow, and the social title, description and image, but not what the plugin makes from its templates. More on WordPress to Umbraco.
Contentful to Umbraco
Reloque reads the space through its Content Management API, in every status and every locale. Contentful has no built-in posts or pages, so content types are told apart by name and fields: a type for posts, one for pages, your own types as types of their own, authors, and categories and tags, with Contentful's own tags too. Assets come as media. Rich Text keeps its headings, lists, links, formatting and images, and links between entries point at the moved records. SEO fields, or an SEO entry an entry links to, reach the other CMS's SEO fields, and menu and redirect entries come as menus and redirects. More on Contentful to Umbraco.
Sanity to Umbraco
Reloque reads the dataset through Sanity's API, drafts included. Sanity keeps its schema in the Studio's code, so document types and their fields are read from the documents themselves, and told apart by name and fields: a type for posts, one for pages, your own types as types of their own, authors, and categories and tags. Images and files come as media. Portable Text keeps its headings, lists, links, formatting and images, and references between documents point at the moved records. Translations made with document internationalisation come as each record's languages, an SEO object reaches the other CMS's SEO fields, and menu and redirect documents come as menus and redirects. More on Sanity to Umbraco.
Webflow to Umbraco
Reloque reads the site's collections with their fields, and every item, drafts included. Posts, your own collections, authors and categories are told apart by name and fields, references come with what they point at, and categories keep their parents. Images and files come as media, rich text keeps its headings, lists, links, formatting and images, and links between items point at the moved records. SEO fields reach the other CMS's SEO fields, and static pages come as pages with their text, images and SEO settings. More on Webflow to Umbraco.
Payload to Umbraco
Reloque reads your collections, uploads and relationships with a user's API key, from Payload 1, 2 or 3, with blocks, arrays and groups read as structured content, not flattened. A localized site is read in every locale, and its globals (site settings, header, footer) go to the new site's globals or single types of the same name. A header's or footer's links become menus on WordPress, and the redirects plugin's redirects move too, each to its page's new address. Payload has no front end, so you can give the public site's address when connecting, and links to it in the content are pointed at the migrated records. More on Payload to Umbraco.
Strapi to Umbraco
Reloque reads your content types, media and relations with an API token, or as a Users & Permissions user on Strapi 3. Rich text in blocks or Markdown is read as formatting, not as raw text. A translated type is read in every locale, each published or a draft as it is. Single types, such as the site's settings, go to the new site's single types or globals of the same name, and their lists of links become menus on WordPress. Redirects come too, from a Redirect type of your own or strapi-plugin-redirects on Strapi 4. More on Strapi to Umbraco.
Ghost to Umbraco
Reloque reads posts, pages, tags, authors, images and each one's SEO and sharing fields through the Admin API, from Ghost 3 to 6, or from an export file. The navigation and secondary navigation come too, from Ghost 5 and later or an export file, with their links pointed at the moved pages, and so do comments, with their replies, from Ghost 5 and later. Connected with a staff access token, the site's redirects come too. More on Ghost to Umbraco.
Drupal to Umbraco
Reloque reads every content type's nodes through JSON:API, or the bridge file on Drupal 6 to 8.6: articles as posts, basic pages as pages, your own types as types of their own, with their fields, Paragraphs as blocks, Media and files, every vocabulary's terms and each node's author. SEO data comes from Metatag: the tags an editor set for a node, not Metatag's defaults, so it reaches the other CMS's SEO fields. Members come too when you choose them: users who only visit the site, never your editors, with their roles and fields but never their passwords. Menus come too, with each link pointed at the moved page, and comments with their replies, visitors' names and emails, and whether each was approved. Every language comes too: each node with its translations, in their own titles, aliases and fields. So do the Redirect module's redirects, each pointed at its page's new address, and the site's name, slogan, language, logo and icon. Links between nodes point at their aliases. More on Drupal to Umbraco.
Storyblok to Umbraco
Reloque reads the space's content types from its components, and every story with its content, drafts and every language included. Posts, pages, your own content types, authors and categories are told apart by name and fields, and Storyblok's own tags come too. Components inside stories move as blocks, assets come as media, and rich text keeps its headings, lists, links, formatting and images, with links between stories pointing at the moved records. SEO fields reach the other CMS's SEO fields, a config story's navigation comes as menus, and redirect stories as redirects. More on Storyblok to Umbraco.
Planned routes
These connectors are planned. Each guide says what to weigh and plan in the meantime.
What moves from Umbraco
Reloque scans your Umbraco site first, maps each field to the destination and previews the move on it before the live run.
- Documents and document types
- Media
- Nested Content, Block List and the Grid
- Pickers and links between pages
- Package editors: Contentment, Archetype, Doc Type Grid Editor
- Members, when you choose them
How Umbraco works
Umbraco organises content as nodes in a tree, each based on a document type that defines its properties. Media is kept in a media library, and developers build templates and extend the back office in C#.
Who uses Umbraco
Agencies and in-house teams that already work in .NET use Umbraco for company websites and intranets. It fits organisations standardised on the Microsoft stack.
What Umbraco does well
Fits .NET teams
Built on tools .NET developers already know.
Editor-friendly back office
Editors get a clear interface for content and media.
Flexible document types
Developers shape the content model to each project.
Cloud or self-hosted
Run it yourself or use Umbraco Cloud.
What to weigh before you move
No CMS fits every team. These are the points that come up most when people plan to leave Umbraco, or to make it their next home.
- Needs .NET skillsCustomisation is done in C#.
- A smaller ecosystemThere are fewer ready-made extensions than on the largest platforms.
- Hosting needsSelf-hosted sites need a .NET-capable environment.
What does not move yet
Better to know now than after the switch. The scan names anything it finds that cannot move.
- Members move between every CMS here, and never with their passwords.
- Umbraco's navigation is its page tree, so menus from another CMS are listed in the handover package to set up by hand.
- Umbraco has no comments of its own, so comments from another CMS are listed in the handover package.
- SEO properties are known by their names, such as seoTitle, metaDescription and noIndex; one named otherwise is matched on the Map step as a field of its own.
- Umbraco 7 to 14 are sources; writing needs Umbraco 15 or later.
Planning a move from Umbraco
In Umbraco the content tree and document types describe your structure, so start there.
- List document types and their properties
- Review the content tree and how pages are nested
- Check language variants and domains
- Note media items and redirects
Umbraco questions
What is Umbraco?
Umbraco is an open-source CMS built on Microsoft .NET. Developers define document types, and editors manage content in a friendly back office.
Who uses Umbraco?
Agencies and in-house teams that already work in .NET use Umbraco for company websites and intranets. It fits organisations standardised on the Microsoft stack.
What content can be migrated from Umbraco?
Documents with their document types and property values, media, links between pages and, when you choose them, members. Editors are converted between versions: Nested Content, the Grid, pickers and the Contentment, Archetype and Doc Type Grid Editor packages.
What should I prepare before migrating from Umbraco?
In Umbraco the content tree and document types describe your structure, so start there. Four checks help most: (1) list document types and their properties; (2) review the content tree and how pages are nested; (3) check language variants and domains; (4) note media items and redirects.
Can Reloque upgrade Umbraco 8 to Umbraco 17?
Yes, as a migration rather than an in-place upgrade. Reloque reads the Umbraco 8 site through the bridge template and writes into a new Umbraco 15 to 18 site, converting each editor's values: Nested Content becomes a Block List, the Grid becomes rich text, and media and page pickers point at the migrated items.
Do Umbraco members move?
When you choose to, between Umbraco sites. Names, emails, groups and their own fields move, but passwords cannot, so each member sets a new one with the site's forgotten password page. The handover package lists them.
Can Reloque migrate Umbraco today?
Yes. Umbraco 15 to 18 connect with an API user, as a source and a destination. Umbraco 12 to 14 are read through the Delivery API, and 7 to 13 through the Reloque bridge template. Routes run to and from WordPress, Payload, Strapi, Ghost, Drupal and another Umbraco site, so moving an old Umbraco site onto a current version is a route too.