@Valdis, I'm new to episerver and do not know what migration step you are referring to.
I had these in mind - https://world.episerver.com/documentation/class-library/?documentId=cms/7/49ffb44e-34fc-c91a-8cb3-e107c036767a
Also collegue of mine blog post would become helpful - https://www.patrickvankleef.com/2015/08/18/episerver-content-migration/
This seems wayyyy too involved/complex to simply update a property type.
Isn't there a way to simply update a page type in the epi databasae?
Why did Episerver make this so complex/cumbersome?
Did they think developers would never need to update a property on a page type?
If you made the changes in code you can go into the CMS->Admin->Content Type->Page Types and apply your changes, IF you don't mind data loss. If I am correct on your properties there should be a button "Revert to Default" that will do exactly what you are asking for.
In code you could load the type from IContentTypeRepository and attempt to modify it. Again the function ResetContentType might do exactly what you want but i have never tried it myself.
This is during -development- where data loss isn't an issue. If you have deployed the old type into a staging or production environment you need to use migration steps.
It is cumbersome to avoid data loss when altering data types in an sql database, it has more to do with sql than Episerver.
How do you convert old page type properties to new ones?
Say I have this class
and want to cahnge the string to XhtmlString and VideoFiles to a certain blcok
If I go to episerver, log in and view this page in edit mode, these new property types do not reflect.
Why?
And what is the best way to convert them to the new types?