Moving programs can be a pain sometimes.
1. Make sure the form is within the program and not in design studio. This way the cloned program won't reference a form in a different workspace.
2. I still see pages (and maybe emails). A page is based on a template. That template is propably in Design Studio in that other workspace. You have two options:
A. Put that template in a folder and share that folder with the workspace you are migrating too. I think that could fix your issue, but I'm not 100% sure.
B. You clone the needed email and page templates to a folder in the new workspace. Then share that folder with your current workspace. Then update your email center's assets with that new template. Now your center is using templates from the new workspace, so you should be able to move your program to the new workspace (with that I mean, you can move the folder that contains your program. That's even better than cloning).
Thanks so much Diederik!
Your suggestions were helpful and I have managed to get through the association errors however now I am faced with a new challenge.
When I move the folder (drag and drop the folder with the subscription center program from the current workspace to the new Global workspace), I get this new error and I don't know how to resolve it. I am hoping you might have a suggestion?
Thanks in advance!
I haven't seen that error before. You could try to remove that line and recreate it after moving. Else I'd suggest contacten support to get some context.
Jennifer - we've been seeing more and more of these "Webform ID" errors when trying to clone program templates (those that contain local forms) from our "center of excellence" workspace to different country workspaces. When we opened a ticket with support they came back telling us that you cannot clone/move programs that contain local forms. Which, as you probably know, is not true. Now if the form is contained in design studio, that is true - especially since you cannot share forms across workspaces.
What we did to resolve this is clone the program to a new program in the same workspace and used that to clone to other workspaces. What happens, over time (for whatever reason), is programs can get corrupt and throw these sorts of errors when trying to move/clone them across workspaces. Give that a shot and let us know if that works for you.