Transfer a workspace to another organization
Hand a whole workspace, and its history, to another organization. It takes two people and a one-time code, so it can't happen by accident.
A workspace holds an Aprimo instance's configuration and everything Mochi keeps around it. Sometimes the organization that set a workspace up isn't the one that should own it. A partner builds a workspace for a customer, or an internal team hands one to the group that will run it. Transferring the workspace moves it, and its full history, to the other organization.
It's deliberate on purpose. One person issues a code, gives it to the other, and the two of them complete the move together. Nothing changes until the current owner approves it.
Before you start
- You need to be an owner of the workspace and an admin of the organization that owns it now.
- The person receiving it needs a Mochi account and must be an admin of the organization that will own it.
- The workspace needs to be settled. Finish or cancel anything being delivered, and clear any change sets waiting for approval, before you start.
Transfer a workspace
- Open the workspace's Settings and choose Transfer. Then choose Create a transfer code.
- Copy the code. Mochi shows it once. Keep it somewhere safe.
- Give the code to the person who will own the workspace. Share it the way you would anything private. Anyone with the code can start the handover, so treat it like a password.
- They enter it in their own organization. On their workspaces page they choose Have a transfer code? and enter the code. This doesn't move anything yet.
- Approve the transfer. Mochi emails you that someone entered the code. Open the link, type the workspace's name to confirm, and approve. Only then does the workspace move.
What comes across
Everything in the workspace goes with it: its configuration, its full history of change sets, and its environments. The connection each environment uses to reach Aprimo comes across too, so the new owner picks up exactly where things were left, with nothing to reconnect.
What the previous organization keeps and loses
Once the transfer completes, the organization that had the workspace loses access to it. Its people are removed, its API keys for the workspace stop working, and each person's Aprimo sign-in for it is reset. The new owner adds their own people and sets up access as they see fit.
The old organization keeps its own record that the transfer happened. What it can no longer do is open or change the workspace.
Backing out
- Before the code is entered: open Transfer in the workspace's Settings and choose Cancel transfer. The code stops working.
- After it's entered but before you approve: choose Deny. Nothing moves.
- A code lasts three days, and only one transfer can be open for a workspace at a time.
For who can do what, see Roles and access.
