If you are provisioning users into RM Unify via CSV, MIS Sync or a single-school AD Sync installation, then we do not currently support user transfers between RM Unify establishments. The user should be provisioned with a new RM Unify account in their destination school. Their account in the original school will be deleted in the normal process.

If the user has data they would like to port across, e.g., emails, and they are allowed to do so, please ask them to manually export the data before their old account is deleted. They can then import the data when their new account has been provisioned.

Note: For sites that share a Microsoft® 365™ tenancy, we can support the transfer of the user's account from one establishment to the other. This requires an account in each establishment for us to action the change.

If you are provisioning users into RM Unify via a multi-school/multi-site AD Sync installation, then you will see the following user transfer behaviour:

• User transferred to/from child sites, e.g., School B to School C:
  • the user correctly transfers from School B to School C in the AD Sync Config Tool.
  • the user shows in the new school's RM Unify Management Console and their username is updated, e.g., JSmith@SchoolB becomes JSmith@SchoolC.
  • update messages are sent to apps deployed in the new school.
  • delete messages are not sent to apps deployed in the old school.
• User transferred to/from the parent site, e.g., School B to School Trust:
  • the user correctly transfers from School B to School Trust in AD Sync Config Tool.
  • the user does not transfer in RM Unify and remains a user in the original school's RM Unify Management Console.

The RM Cloud Support team can assist with transferring users to/from a parent site once the user has successfully transferred in the AD Sync Config Tool. Please raise a support request with your usual network provider.