Migration routeIn early access

Move content between two Umbraco sites

Reloque copies posts, pages, media, SEO data and redirects from one Umbraco site to another. It maps every field, previews every record and tests a sample on the new site before the real move.

Join early access Free for early-access members: we look at your Umbraco site with you before anything moves.

What Reloque reads from Umbraco

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).

How it lands on the other Umbraco site

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 8 editors, written into Umbraco 17

Umbraco 8 editors, written into Umbraco 17
UmbracobecomesUmbraco
Nested ContentBlock List
Grid layoutRich text, with its blocks
Media Picker (ids)Media Picker, re-picked by key
Content PickerDocument Picker, to the migrated page
Contentment Content BlocksBlocks
Image CropperImage Cropper, file and crops uploaded
MembersMembers, without passwords
How the values of retired editors are rewritten for a current Umbraco. Each property is read in its own version's format and written in the format the new editor takes.

What to plan for

Better to know now than after the switch. The free scan names anything on your site that cannot move.

  • Umbraco: Members move between every CMS here, and never with their passwords.
  • Umbraco: Umbraco's navigation is its page tree, so menus from another CMS are listed in the handover package to set up by hand.
  • Umbraco: Umbraco has no comments of its own, so comments from another CMS are listed in the handover package.
  • Umbraco: 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: Umbraco 7 to 14 are sources; writing needs Umbraco 15 or later.

Versions checked

  • Umbraco: Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).

Questions

Can Reloque move content between two Umbraco sites?

Yes. Reloque moves content between two Umbraco sites, for early-access members now. Checked on Umbraco 18, 17, 16 and 15, and 14 down to 10 as sources (7 to 9 compiled against).

What does a migration between two Umbraco sites cost?

The assessment is free and gives your exact price: you pay for the records a migration writes, and media files do not count. Packages start at £99, and records are shared across any number of migrations for 12 months.

Will my addresses and SEO survive the move?

Every address that changes gets a redirect, written to Umbraco where it keeps redirects, or ready as a CSV for your host or front end. SEO titles, descriptions and social images move where Umbraco has a place for them.

Is anything written to Umbraco before I approve it?

No. You see every record in the Preview first, then a small sample is written to Umbraco so you can check it on the real site, and undo it. Umbraco is only ever read.

Early access

Planning this move?

Reserve a free assessment and tell us you are moving Umbraco to Umbraco. We will look at your site with you before anything moves.

Plan this move with us

Early access is free. Tell us both systems when you reserve.

Free assessment

Moving between Umbraco sites?

Reserve a free assessment and we look at your Umbraco site with you: what moves to Umbraco, what stays, and the price. Nothing is written until you approve it.

Get your free assessment
Early-access members get a free migration assessment.
  1. Connect both sitesReloque reads the source and checks it may write to the destination.
  2. Check the mappingEvery field is matched, and the uncertain ones are yours to decide.
  3. Test a sampleA few records are written to the destination, read back and removed.
  4. Move the restEvery record is written and checked, with redirects for old addresses.