the problem you have is moving a property between content types is actually a delete and re-create in the background, and the delete will cause a refresh of all the content (so it will delete the content values!). then the create will put the new value in, but the content values will be gone. 😦 doing it with uSync (and the content files) means the delete does happen but when you import uSync puts the content back in because it has it outside the DB. i don't think there are non-hacky ways to do this, because via the api will trigger the internal notifications that do all the cleanup.

(it is possible to suppress notifications, which might stop the delete from popergaing but i am not 100% sure that will work in this case (not all notifications are supressible)

ah no, that just changes the doctype.. never mind 🙈

I asked Co-Pilot for a programatic solution which I assume it got from someone who has done this

csharp
    var contentService = Services.ContentService;
    var allContent = contentService.GetRootContent().DescendantsOrSelf();
    
    foreach (var content in allContent)
    {
        if (content.HasProperty("oldPropertyAlias") && content.HasProperty("newPropertyAlias"))
        {
            var oldValue = content.GetValue("oldPropertyAlias");
            content.SetValue("newPropertyAlias", oldValue);
            contentService.SaveAndPublish(content);
        }
    }

At least it is only copying so I can test it's all there.

You can fiddle with the database instead and that should probably work, but it WILL confuse Umbraco Deploy, so you will need to resave the affected doctypes and then it might work. But I would then also fiddle with the Cloud database to do the same to prevent anything from messing up.

But definitely make copious backups before you do anything 😅

(I've used it heavily in the past)

Although.. watch out because the last part of that does say "just don't try that on cloud.. because it will break your deployments"

You shut down umbraco, fiddle with the SQL, delete all temp files and wake up umbraco and it should accept it's new reality 🙂

This looks both very clever and really scary! For now I am composing them into the same named tabs and groups so at least from the editors perspective common properties are grouped nicely. However, for the devs and site managers not so nice.