Managing Users Migrating from a Self-Hosted to a Hosted Instance
About Migrations
Before a self-hosted instance can be migrated to a hosted instance, there are some questions that must be answered and actions taken in order to facilitate the migration. All users in self-hosted OfficeMaps will have a user name and password that is either manually maintained or is integrated with Active Directory. To migrate to a hosted instance, we will need to map existing user names to the user name format for the hosted instance.
The most important consideration is the method that will be used for accessing hosted OfficeMaps. This can be done in one of two ways: manually entered (non-integrated) user names and passwords; or an Azure AD / Office 365 integration. Read the section that corresponds to your requirements.
Manually Entered User Names and Passwords
Steps you will need to take before the migration:
- If the current instance is integrated with Active Directory, the client technical contact will first need to be assigned a non-integrated user name and password so that they can connect to the instance once it becomes a hosted instance.
Steps you will need to take after the migration:
- Under the People -> Preferences menu option, ensure that the default login method for all users is set to "Login with OfficeMaps username and password".
Azure AD / Office 365 integration
Steps you will need to take before the migration:
- If the current instance is integrated with Active Directory, the client technical contact will first need to be assigned a non-integrated user name and password so that they can connect to the instance once it becomes a hosted instance.
- You will need to create a group in Azure AD containing all the members that will access the hosted OfficeMaps instance. All current users in OfficeMaps must be added to the group or set to disabled / non users.
- Is there a consistent naming convention that allows for a match to be made between the current user name in OfficeMaps and the new Azure AD / Office 365 account name? One simple example of this is the case where all user names correspond to the user's email address. If there is no consistency, you must create a spreadsheet listing all the current user names in OfficeMaps and a corresponding value for the account name in Azure AD / Office 365.
- The client technical contact will need to be on hand at the time of migration in order to provide integration details and confirm that the sync has completed successfully.
Steps you will need to take after the migration:
- Under the People -> Preferences menu option, ensure that the default login method for all users is set to "Login with Azure AD".
- If the current instance is integrated with Active Directory, the technical contact's user name must changed to be the same as their integrated user name.
Related Articles
Steps for Migration from a Self-Hosted Instance to Hosted OfficeMaps
The process to move OfficeMaps from a self-hosted instance to a hosted one requires a number of steps. 1. Verify that your self-hosted instance is fully updated with all the system requirements to run the current self-hosted version of OfficeMaps. ...
Configuring Azure AD for self-hosted OfficeMaps
This article is intended to provide network administrators with the steps required to enable Azure AD to integrate with self-hosted OfficeMaps. IMPORTANT: THIS ARTICLE IS ONLY FOR ON-PREMISE INSTANCES. DO NOT COMPLETE ANY OF THESE STEPS IF YOUR ...
Self Hosted Upgrade Procedure
The self-hosted version of OfficeMaps consists primarily of the OfficeMaps folder (assuming web sites and files etc. are still contained within) and the SQL Database. The overview of the upgrade process is: Download and copy upgrade ...
Using Zapier to Update Users
By using the OfficeMaps Zapier integration you can update user details from over 2000 other applications including Slack, SQL Server, G Suite, IMAP Email Servers, and AWS. Prerequisites: Before starting you will need to have a Zapier account and have ...
Using Zapier to Create Users
By using the OfficeMaps Zapier integration you can create users from over 2000 other applications including Slack, SQL Server, G Suite, IMAP Email Servers, and AWS. Before starting you will need to have a Zapier account and have connected it to your ...