Hi Matt,

You are correct, member-types are the same as document-types.  Once you create a member, you can't change their member-type!

There are a couple of ways to tackle your problem:

• Duplicate the "Artist" fields for the "Member" (along with another field for "upgraded", so you can distinguish them).

• Develop code to upgrade a "Member" to an "Artist", meaning that you would create a new member (based on the "Artist" member-type) and copy across the original "Member" data ... then delete the original member.  Obviously this may knacker any other business logic you may have that deals with member Ids?

Cheers, Lee.

Hmmm, I guess you could go with the second option, and on the entity store "PreviousID" or something so you can tie any data back to the new entity?

Matt

I think I would go with the role based approach so you have a tab with "Member" info, and one with "Artist" info, and then decide which fields to show based on the groups they are members of.

Alternatively, if you don't want to clutter your membertype, then you could just have the basic info in there, and get the profile data from somewhere else (custom db table). This would probably scale a bit better if you decide to add more groups in the future which all need different info on them.

To answer the original question: I guess the safe way would be to copy the members from one memberType to another, and then delete the original member via the Umbraco API. In version 8 the following code should work:

The code below is copied from the following repo: https://gitlab.com/umbracohowto/ourumbraco7497

private static readonly string targetMemberContentTypeAlias = "Member";
private static readonly string sourceMemberContentTypeAlias = "specialMember";
private static readonly string processedMemberPrefix = $"{targetMemberContentTypeAlias} # ";


var targetMembers = Services.MemberService.GetMembersByMemberType(targetMemberContentTypeAlias).Where(m => !m.Name.StartsWith(processedMemberPrefix));
    foreach (var member in targetMembers)
    {
            var newMember = Services.MemberService.CreateWithIdentity(member.Username, member.Email, member.RawPasswordValue, sourceMemberContentTypeAlias);

            member.Name = $"{processedMemberPrefix}{member.Name}";
            member.Username = $"{processedMemberPrefix}{member.Username}";
            Services.MemberService.Save(member);
            Services.MemberService.Delete(member);

    }

is working on a reply...