Okay, before going through all that, my ultimate goal or issue is when I apply a User Mapping from a global security login user "iuser" to a database and I got the following error.
Create failed for User 'iuser'. (Microsoft.SqlServer.Smo)
User, group, or role 'iuser' already exists in the current database. (Microsoft SQL Server, Error: 15023)
The local user "iuser" is already imported along with the database. In the past, I simply delete the 'iuser" from the local database and then re-apply the user mapping from the global login user. However, in this case, I can't because it is tied to a schema and that schema is then tied to an object. If there is a way to resolve my initial issue, I don't need to transfer the objects another schema.