Moving Team Projects between the new Adobe profiles

Posting here again to share my recent experience with the need to transfer team projects from one profile to another.

Some background: At some point in recent history, my organization wound up running two adobe business accounts with two admin consoles (one for office/sales apps like Sign and Acrobat, the other for designers/editors using Creative Cloud). This means we got two bills from Adobe every month, which our financial department wasn't super thrilled with, so we decided to "merge" the two accounts into one. Essentially it boiled down to purchasing Creative Cloud licenses on the "office/sales" account and moving the design/editing users over to that.

My team and I work primarily with Adobe Team projects thanks to the excellent collaborative convenience. So, once it came time for the transition I use my adobe account as the guinea pig and switched over to the "new" profile created for me after adding my account to the new admin console and attributing a creative cloud license to it. I do the typical sign out of the creative cloud app and sign back in to switch profiles (by the way, why isn't there a "switch profiles" button yet? Netflix has this figured out but for Adobe we need to fully sign out and then back in?) Lo and behold, the team projects did NOT follow me to the new profile. Not all that surprising considering it IS a new profile and as far as Adobe knows this could be a completely different business so of course the Team Projects wouldn't transfer. The problem is I want them to. Cue the rabbit hole.

First I come across this thread which shows me that I'm not alone in the need to migrate team projects between profiles for similar situations, whether it's between a personal profile or two business profiles. And it's also promising to see that there are engineering and support staff from Adobe who were active in this thread, clearly this is getting attention. The most recent post when I got here was from adobe employee @Udo_Pawlik who shared a support article from 2022 titled "Migration issues when using Team Projects" describing how to access the "Team Projects Manager" window in Premiere. It described essentially needing to open a beta version of Premiere patched using files provided to the user from an Adobe representative.

At this point I needed to pause the migration project because it's clearly a larger lift than originally anticipated and my team and I had active projects that needed to be finished by the end of the month so we chose to stick to the old business profile until then.

Fast forward to now and I begin the project of contacting Adobe support to get this sorted out. In preparation, I went to return to the "Migration issues when using Team Projects" support article only to find it now showing a 404 page. Not promising. I was able to screenshot it before losing access, for archival purposes (and because I now have a bit of a tin hat and bone to pick about this whole thing) I'm adding the screenshots of the article here:

Still confident that someone over at Adobe will be able to help with the migration, I begin the saga of chatting with the support team. I'll keep this brief, but yikes, it did NOT go as I expected. I started by using the support text chat, after an entirely unhelpful conversation with the AI bot, I began talking to what I believe were genuine support agents. I linked them back to this forum post and explained that I needed help migrating Team Projects to the new profile. Unfortunately my experience consisted of the agents repeatedly disconnecting from the chat on me, but not before some linked me back to the "Transfer Files across Accounts and Profiles" help page that OP mentioned at the top of this thread (proving that the agents didn't take the time to view this thread that I was referencing) and all but one shared a hilariously obvious copy-paste message about how they "have X years of experience" and "have seen this issue before with other customers." Kindling for the frustration fire that was building with every sudden support agent disconnect.

So the text chat wasn't working. I moved on to the support phone line. I'll not linger on the annoyances I dealt with there which included needing to explain to one agent that team projects are NOT stored on my computer and the classic "I gave my email address to the first agent then got transferred to a second who then asked for my email" issue that plagues support lines nowadays.

Eventually I finally got to someone who was specifically a Premiere Pro agent. After a bit of back and forth about the workaround of offlining projects as standalone .prproj and .aep project files and re-importing into a team project, I explained what I found in this thread as well as the "Migration Issues When Using Team Projects" support article which implied that there was a way to do the migration without needing the workaround which would come with the downsides that @michaelgoshey described in his first post to this thread. The support agent then insisted that there is no way to do this, despite the evidence in this thread that at one point it was.

In the end I'm left extremely frustrated after a generally rough time dealing with Adobe Support that my only option is to use the not-so-great workaround to migrate my team projects despite the 2-3 year old posts in this thread implying that it wasn't always the case and that there were people at Adobe actively working on a more permanent solution. I'm planning to pester our Adobe sales rep about this to hopefully try to figure out what the deal is and I'll update my post here with any additional findings. If anyone else in the thread has any further or more recent information on the topic, I'd love to know what your experience was like too. Hopefully this long post also helps anyone else in a similar situation know what the current state of team project migration looks like.

TL;DR all of the previous conversation in this thread is mostly very out of date and seemingly forgotten about by Adobe. Support only knows about the workaround of using the "Edit>Team Project>Convert Team Project To Project..." function to create a local offline project then re-importing that into a new team project created on the new profile that users are trying to migrate to.

I second all of this. We are in the exact same situation and it's not reasonable. It's not a reasonable solution to ask customers paying you thousands of dollars a month for software to "use a work around"

We need a proper resolution to this problem.

Hi!

Sorry to hear about the migration issues you are seeing related to Team Projects.

This issue is a known problem by our core cloud services team and we have been in discussions with them. Basically, when the migration occurs, if your Adobe ID / Profile is associated with more than one business profile the migration program doesn't know which profile your Team Project should go into. When this happens it leaves the Team Project in the core user profile and does not migrate to any business profile that your Adobe ID is a member of. And this can be confusing no doubt.

One possible work around is to export your Team Project to a stand-alone Premiere Pro project (prproj on local disk), then log into the business account / profile with your Adobe ID that you want the Team Project to show up under and then create a team project from that prproj file. While this will work and create a copy of your Team Project into the business profile, there are a few details/limitations to be aware of:

1. Any After Effects comps used in your sequences will not go along for the ride when you saved the Team Project as a prproj. Thus, they won't be available in your new Team Project. You would need to manually replace the comps after moving the Team Project into the business profile.

2. All history associated with the Team Project will not transfer to the prproj and thus not be part of the new Team Project created in the business profile Team Project.

We realize the inconvenience and distraction this causes and sincerely apologize. While we continue to work with our cloud services team on a resolution, we don't see one immediately available that would automatically migrate the projects for you. Ideally what we'd like to offer you is a list of Team Projects with the ability for you to determine where to migrate each project (to which profile). But as mentioned, this doesn't look likely anytime soon.

I believe your conclusions about the tech support direction you received is accurate. They appear to be thinking about Cloud Documents and not Team Projects. Team Projects do not live in the same location as Cloud Documents and thus are not readily available from any browser interface in Creative Cloud.

I would like to also state that losing your projects is not going to happen - and you will not lose access to any projects. The pain point here, of course, is that you will need to select differnet logins to see your older projects that didn't migrate into your particular businsess profiles. But rest assured the projects still exist and you will still have full access to them when logged into the appropriate profiles.

Again, we are deeply sorry for this inconvenience. We are continuing to work for a solution and will share that here once we have something available.

Regards,

Michael

Sr. Engineering Manager

Adobe Team Projects

@mgoshey1  ... got any ideas here?

Neil