🚀 go-pugleaf

I was able to get mine going by doing a couple things ,most of which probably have almost nothing to do with the issue.

I wanted to add a new user, so I adjusted the workgroup size for VC CS4 in System Prefs. I used a Mac admin account to log into my VC CS4 panel as a VC admin. I then created a new VC CS4 user account for one of the other users on this computer. I gave them a group and sorted out the sort of permissions I wanted them to have, then logged into the other user's account on the Mac and launched Adobe Drive to connect.

I set up a few more preferences and logged into the VC CS4 panel with this other user's account to make sure everything looked alright. For some reason at this point I decided to launch VC CS3 from this other users account, and I set it to the same workgroup size as my VC CS4 server.

When I logged back into my Mac admin account and visited the VC CS4 panel, the VC CS3 migration option worked fine. I've migrated all my projects and I haven't noticed any major problems.

I had opened a support case, and when all this happened I updated my case with this new information, and they suggested that I had a permissions issue initially. However, I think they also thought this other user account was an admin- it isn't.

So basically, I set up a new VC CS4 account fully, then logged into it using the other Mac user (not admin) account. From this other account, I connected to my VC CS4 server and launched the VC CS3 server. When I logged back into my account, the migration worked fine.

I am sure a lot of those steps are unnecessary, and there's a good chance that none of it had anything to do with resolving my issue; but it worked for me and I hope it works for someone else.