Umbraco upgrade from U13 to U17

[JeetRawani]

Hi All,

I have less experience in Umbraco application and need support.

I am trying to upgrade our project from U 13.13.1 to U 14.3.2, but having multiple challenges.

1. I have nested block, So I use to convert it to Block list. I used AutoBlockList, having few challenges and issue.
   a) I have 1183 content supporting and in once we are able to select only 10 then next page and select another. Is there any way to do in single go?
   b) After convert via AutoBlocklist, in backoffice Some of block list message like “The properties type is no longer available” and others working fine.
   please see below screenshots.

   

   c) Also, I tried to use uSycn.migration(4.0.0-phase.5.2) to export, but only able to select and export option not able to find. Complete download option present.
   d) If point (c) work then how we import, using uSync? because uSync.migration not visible in Umbraco17?
   e) Tried Umbraco.Community.LegacyFeatureConverter 13.0.0-beta.4 as well but getting error:
   Microsoft.Data.SqlClient.SqlException
   HResult=0x80131904
   Message=Column ‘Id’ in table ‘LegacyFeatureConverterHistory’ is of a type that is invalid for use as a key column in an index.

2. How we convert Umbraco.Grid, any tools or need to create custom code?

3. Can we directly do Media Picker migration (U13 → U17), using uSycn?

4. I also got textbox related error so I updated with below code:
   UPDATE umbracoDataType
   SET config = ‘{“maxChars”: 0, “placeholder”: “”}’
   WHERE propertyEditorAlias = ‘Umbraco.TextBox’;

5. Localhost:port → No physical template file was found for template Home, no any details error available for home page.

[justin-nevitech (Justin Neville)]

Hi @JeetRawani

Welcome to the forum!

You will need to converted Nested Content to Block List before you move beyond Umbraco 13.

Follow these steps:

1. Update to the latest Umbraco 13
2. Install uSync Migrations for Umbraco 13 (you will need the select the pre-releases tickbox on Nuget)
3. Run uSync and do a full export of both schema and content
4. Run uSync Migrations and create a new migration (leave all the defaults). This will write a new set of uSync files to disk - it does not change anything in the database yet.
5. Once the migration has run, import the schema changes from the migration and restart the site
6. Once restarted, import the content changes from the migration

You will then have a site with Nested Content migrated to Block List and Grid Layout migration to Block Grid (if you used that). There may still be other things you need to migrate, such as macros to RTE blocks and migrate legacy/obsolete data types but this should get you most of the way.

If you have custom backoffice code, you will need to migrate that from Angular to Web Components.

Once done, you can then migrate directly to Umbraco 17 from 13, no need to go to 14 first (and in fact 14 is EOL).

I hope that helps!

Justin

[JeetRawani]

Hi @justin-nevitech , Thank you for your support.

Point 4. Please suggest given steps are correct or need to change..

I clicked convert button and selected Migration details and submit. After that one migration folder created with below details: file name - _.status
{
“icon”: “icon-nodes”,
“root”: “C:\Projects\proj_name\bin\uSync\Migrate\site-conversion-profile”,
“id”: “site-conversion-profile”,
“version”: -1,
“name”: “Site Conversion profile”,
“source”: “uSync/v9”,
“siteFolder”: “/”,
“target”: “uSync/Migrations/20260605_213034”,
“migrated”: false,
“importStatus”: {},
“plan”: “BlockMigrationPlan”,
“clientId”: “”
}

Now I need to upgrade U13 to U17 dll and run migration or missing anything?

Also, source and targe path will be same as uSync, currently it is “RootFolder": "../uSync13/Root/“?

[justin-nevitech (Justin Neville)]

Hi @JeetRawani

Once you’ve click migrate (or convert the button may say), you then need to import the migrated schema and content files to actually update the database. You need to do this before you attempt to go beyond Umbraco 13.

Justin

[JeetRawani]

Hi @justin-nevitech, uSync migration completed and nested content converted to block list. But after upgrade to U17, I am getting MediaPicker issue.

Error : Could not find an editor with alias Umbraco.MediaPicker, treating as Missing. The site may fail to boot and/or load data types and run.

I tried to convert it using custom code but not worked. Kindly suggest, is it also done using uSync or any other way we can do?

[justin-nevitech (Justin Neville)]

Hi @JeetRawani

You will need to change any obsolete media pickers to newer MediaPicker3 before you can move to v17. The older media pickers are deprecated.

As far as I’m aware, the newer media pickers should still work with the older data so they are backwards compatible from that perspective but your templates will need amending.

Justin

[JeetRawani]

Hi @justin-nevitech , Can we directly update media pickers in backoffice, Is there any data lose?

And updating template code changes.
Still having few error and I am fixing those as well:

1. ERR] Exception (37ca8a79).
   Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name ‘performingUserKey’.

2. [17:02:41 ERR] Exception (3bf1911c).
   Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name ‘description’.

3. [ERR] Migration failed for property type: Blocks (id: 184, alias: blocks, editor alias: Umbraco.BlockList)
   System.InvalidOperationException: The configuration for data type 7083 : Umbraco.TextBox is invalid (see inner exception). Please fix the configuration and ensure it is valid. The site may fail to start and / or load data types and run.
   —> System.InvalidOperationException: Failed to parse configuration “System.Collections.Generic.Dictionary`2[System.String,System.Object]” as “TextboxConfiguration” (see inner exception).

[justin-nevitech (Justin Neville)]

Hi @JeetRawani

Yes, you can just swap out data types and they should be backwards compatible for the media picker.

Regarding the database errors, that looks like something has failed to migrated - were you able to migrate from the latest 13 (after running uSync Migrations) to v17 and did this work successfully at the time? Is suspect something may have failed and left you in an inconsistent state. Are you able to try the process again?

Justin

[JeetRawani]

Hi @justin-nevitech ,

Two type of error I am getting at the time of migration from latest v13 to 17.

[ERR] Exception (699c41b6).
Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name ‘description’.

[ERR] Exception (a183743d).
Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name ‘performingUserKey’.
Invalid column name ‘affectedUserKey’.

After migration We received below error:

[ERR] Failed to add property ‘blocks’ to index for content 1368

Save and Publish button under content section is not working and giving error - Exception (8b8cf82e).
System.InvalidOperationException: The given ColumnName ‘propertyTypeId’ does not match up with any column in data source.

[ERR] Index populating failed for populator Umbraco.Cms.Infrastructure.Examine.PublishedContentIndexPopulator

[justin-nevitech (Justin Neville)]

Hi @JeetRawani

Those missing columns (performingUserKey, affectedUserKey, description) are all added by Umbraco’s upgrade migrations going from 13 to 17 - so if v17 says they don’t exist, the upgrade never completed against the database. That’s why save/publish and indexing are failing too. Rather than patching columns one by one, I’d go back to a known-good latest v13, confirm uSync Migrations ran cleanly there, then run the v17 upgrade against a fresh copy in one pass and watch the logs until it finishes.

Justin

[JeetRawani]

Hi @justin-nevitech ,

I tried one more time from scratch and I am getting same set of error again. Also, after renaming the properties type column ‘propertytypeId’ to ‘propertyTypeId’ after that we are able to publish content. But still we are getting error ‘No template found and all page showing 404.

[justin-nevitech (Justin Neville)]

Hi @JeetRawani

You shouldn’t have to manually rename your columns, the migrations should handle the database changes for you. You may want to raise this on the Umbraco issue tracker:

Issues · umbraco/Umbraco-CMS

Re the 404 pages, have a look on this thread to see if any of this helps?

Umbraco 13 → 17 upgrade: All pages returning 404 despite published content and valid templates

Hi @Jaics262 Another thing worth checking: we ran into issues using the older-style Program.cs/Startup.cs split on v17 and had to migrate over to the minimal hosting model (top-level statements in a single Program.cs). Might be worth seeing if that’s the cause for you too. Justin

Justin

[JeetRawani]

Hi @justin-nevitech , Not worked above suggestion for me.

During upgrade, I am getting these two error only and not able to find which things causing.

[ERR] Exception (699c41b6).Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name ‘description’.

[ERR] Exception (a183743d).Microsoft.Data.SqlClient.SqlException (0x80131904): Invalid column name ‘performingUserKey’.Invalid column name ‘affectedUserKey’.

Steps followed at the time of upgrade:

1.Update to the latest Umbraco 13

2.Replace mediapicker to mediapicker3 from backoffice

3.Updated textbox:

UPDATE umbracoDataTypeSET config = ‘{}’WHERE propertyEditorAlias = ‘Umbraco.TextBox’;

4.Replace terratype to textbox

5.Ran uSync and did a full export of both schema and content

6.Ran uSync Migrations and created a new migration (leave all the defaults).

7.Once the migration has run, imported the schema changes from the migration and restart the site.

8.Once restarted, imported the content changes from the migration

9.No macros we are using