Cisco provides the following tools to aid the user migration process from Skype for Business/Lync/OCS to IM and Presence Service:

• Export Contact List tool—allows you to export contact lists in bulk from the Microsoft server for migrating users

• Disable Account tool—allows you to disable the Microsoft server account of migrating users

• Delete Account tool—allows you to delete migrating users from the Microsoft server so that presence requests for these users are later routed to IM and Presence Service

These user migration tools can be collectively downloaded as a zip file from the IM and Presence Service Download Software page on cisco.com at http:/​/​software.cisco.com/​download/​release.html?mdfid=286269517&flowid=50462&softwareid=282074312&release=UTILS&relind=AVAILABLE&rellifecycle=&reltype=latest.

The zip file contains the three tools and a text file called version.txt. The text file contains the current version number of the tools and must be saved in the same folder as the tools. If the tools are stored in different folders, you must store a copy of the text file in each location. If the text file is not in the same folder when you run a tool, you receive an error and the tool does not run.

Cisco recommends that you perform the following tasks before you begin to migrate users from Skype for Business/Lync/OCS to IM and Presence Service:

• Set unlimited contact lists and watchers

• Enable automatic authorization of subscription requests

• Disable new subscriber notification pop-ups on Microsoft Lync

The IM and Presence Service IM addresses can be set to match the OCS/Lync SIP URI (msRTCSIP-PrimaryUserAddress) so that the user's identity is maintained throughout the migration. If that is not possible, then user rename is required.

For more information about setting the IM address value for IM and Presence Service nodes in the cluster, see Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager.

Use this procedure to check that the IM address format that is configured on IM and Presence Service aligns with the IM address format of the Microsoft servers.

IM and Presence Service supports two IM address schemes. If you use the Directory URI IM address scheme, the IM address format between IM and Presence Service and the Microsoft servers align. However, if you use the UserID@Default_Domain IM address scheme, misalignment of the IM address schemes is possible.

The UserID@Default_Domain IM address scheme URIs are composed by joining the Cisco Unified Communications Manager user ID with the IM and Presence Service default domain. If any Skype for Business/Lync/OCS URIs do not match the UserID@Default_Domain IM address format, you must modify the URIs of the migrating users. You can modify a batch of Microsoft server URIs before you migrate each batch of Microsoft server users to IM and Presence Service.

Note	For releases earlier than release 10.0(1), you must modify all Microsoft server URIs before the first batch of users are migrated from a Microsoft server to IM and Presence Service.

When the Directory URI IM address scheme is used, Microsoft server users do not have to be renamed if they are from domains that differ from the domains which are configured on the Cisco Unified Communications Manager and IM and Presence Service clusters. Individual users can be assigned a different email domain. You must configure IM and Presence Service for interdomain federation with the Microsoft servers and set up the email for federation feature if the Microsoft server users are on a different domain.

For more information about the SIP URI format, see topics related to maintaining user identity during migration.

For more information about the IM and Presence Service IM address schemes, see Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager.

For more information about setting up interdomain federation between IM and Presence Service and Microsoft servers, see the Interdomain Federation for IM and Presence Service on Cisco Unified Communications Manager guide.

Note

This procedure is necessary only if you modified any Skype for Business/Lync/OCS SIP URIs . For more information about URI formats, see topics related to maintaining user identity during migration. You must complete this procedure before the modified Microsoft server users are enabled for IM and Presence Service. Cisco recommends that you run this tool during a scheduled maintenance window.

Before you can rename the contact IDs for a set of users, you must upload a file containing a list of contact IDs and the corresponding new format of each of those contact IDs. The file must be a CSV file with the following format:

Contact ID, New Contact ID

where Contact ID is the user's IM address as it appears on the Presence Topology User Assignment window.

The following is a sample CSV file with one entry:

Contact ID, New Contact ID
john.smith@example.com, jsmith@example.com

Note	It is your responsibility to compile the CSV file with the appropriate contact IDs. You must ensure that the header Contact ID, New Contact ID is present in all CSV files.

When you run the job, the IM and Presence Service Bulk Administration Tool (BAT) updates the contact lists of any user that referenced the old contact IDs.

Complete the following procedure to upload the CSV file and rename the contact IDs for a list of users.

Note	You must complete this procedure on each IM and Presence Service cluster.

The first step in migrating users from Microsoft Lync or Microsoft Office Communications Server (OCS) to IM and Presence Service is to provision the Microsoft server users on Cisco Unified Communications Manager and license them for IM and Presence Service and an IM and Presence Service supported client.

Note

After users are provisioned on Cisco Unified Communications Manager and IM and Presence Service, Cisco recommends that you complete the full user migration process during the same maintenance window. Leaving users provisioned on both IM and Presence Service and on the Microsoft servers for any time period disrupts message routing for those users.

See Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager for information about configuring new users in Cisco Unified Communications Manager and the license requirements for IM and Presence Service and supported clients.

What To Do Next

Backups of user Lync/​OCS/​LCS contact list information

The Skype for Business/Lync/OCS provides a tool called dbimpexp.exe. Cisco recommends that you use this tool to back up the Microsoft server user contact list information so that you can restore this information on the Microsoft server at a later date, if needed.

For the purpose of migrating Microsoft server users to an IM and Presence Service supported client, you can use this tool to back up the contact list for an individual Microsoft server user or all users.

Related Topic

Usage of the dbimpexp.exe tool: http:/​/​www.ocspedia.com/​Misc/​Explore_​Dbimpexp.aspx?ArticleID=41

What To Do Next

Export of Contact Lists for Migrating Users

Cisco provides an Export Contact List tool (ExportContacts.exe) to allow an administrator to export contact lists in bulk from Skype for Business/Lync/OCS for migrating users. The tool uses the Microsoft server application programming interfaces (APIs) to export contact lists and output to a comma-separated values (CSV) file. This file can then be used by the IM and Presence Service Bulk Administration Tool (BAT) to import these same contact lists into IM and Presence Service at a later point in the migration.

Note

You can run this tool against all the supported Microsoft server platforms. You can run the tool on any Standard Edition server or Enterprise Edition front-end server. To export contact lists for Lync users, the Export Contact List tool requires read access to the Lync RTC database and also read access to LDAP. You must also ensure that dbo execution account privileges are granted to the RTC database. Running this tool has no affect on the capabilities of other Microsoft server users who are signed into Microsoft Lync or Microsoft Office Communicator. However, Cisco recommends that you run this tool during a scheduled maintenance window to reduce the load on the Microsoft server and Active Directory system.

After you run the tool, a file that contains the exported contact lists is created in the same directory as the tool. The filename is ExportedContacts<Timestamp>.csv. A time stamp is appended to the filename when the file is created; therefore, each time you run the Export Contact List tool, it creates a unique output file.

The Export Contact List tool also creates a second file that contains the Microsoft server SIP URI of each user that you specify for the contact list export. The filename is UserList<Timestamp>.txt and it is also created in the same directory as the tool.

Note	You can use the UserList<Timestamp>.txt file as input to the Disable Account tool and the Delete Account tool.

Note	To delete user data from the Skype for Business/Lync/OCS database for migrating users, you must have read/write access to the Microsoft server database.

The Microsoft server provides an administrative way to delete a user from the Microsoft server database. However, if you delete a user from the database in this way, the user is removed from other users’ contact lists. To prevent the user being removed from the contact lists of other Microsoft Lync or Microsoft Office Communicator users, Cisco provides an alternative means of deleting the user from the Microsoft server database.

This alternative tool (DeleteAccount.exe) allows you to delete migrating users so that availability requests for these users are later routed to IM and Presence Service. This tool also ensures that the deleted users are not removed from the contact list of any users that remain on the Microsoft server. Running the Delete Account tool is the second step in a two-step process to disable a migrating user on the Microsoft server. The two-step process is as follows:

1. Disable the Microsoft server account for migrating user.

2. Delete the Microsoft server user data for migrating user.

After you disable the account for migrating user, wait until the Microsoft server's LDAP changes are synchronized before proceeding with the Delete utility. The LDAP synchronization can take up to 30 minutes.

Note

You can run this tool on all supported Microsoft server platforms. You can run this tool on any Standard Edition server or Enterprise Edition pool. Running this tool has no affect on the capabilities of other Microsoft server users who are signed into Microsoft Lync or Microsoft Office Communicator. However, Cisco recommends that you run this tool during a scheduled maintenance window to reduce the load on the Microsoft server and Active Directory system.

The Delete Account tool reads the list of users to delete from an input file. Each line in the input file represents a contact list owner. The contact list owner is represented by the owner’s Microsoft server SIP URI, for example, sip:bobjones@cisco.com. The following is a sample input file:

sip:ann@cisco.com
sip:bob@cisco.com
sip:joe@cisco.com
sip@chuck@cisco.com

You can create your own input file based on the above format. however, Cisco recommends that you use the UserList<Timestamp>.txt file as the input file for the Delete Account tool. The UserList<Timestamp>.txt file does not contain any duplicate, disabled, or nonexistent users.

Running the Delete Account Tool on Standard Edition Deployments

When deleting data for a list of users, you must run this tool once on each Standard Edition server. The database is coresident on the Standard Edition server.

Running the Delete Account Tool on Enterprise Edition Deployments

When deleting data for a list of users, you must run this tool once on each Enterprise Edition pool. The Lync/OCS database instance name to which the Microsoft server's front-end connects must be specified when running the tool.

Caution

For Lync Enterprise Edition, you must run this tool first on the back-end database server and then on each front-end server. The Lync database instance name to which the Lync front-end connects must be specified in both options. The name of the database for the front-end servers is rtclocal. The default name of the database for the back-end server is rtc, but that can be changed during system installation. For OCS Enterprise Edition, the tool must be run on only the back-end database server.

You can use the IM and Presence Service Bulk Administration Tool (BAT) to import Skype for Business/Lync/OCS user contact lists into IM and Presence Service.

Complete the following steps to import the Microsoft server user contact lists into the IM and Presence Service:

1. Upload the CSV File Using BAT.
2. Create a New Bulk Administration Job.
3. Check Results of Bulk Administration Job.

Note

The default contact list import rate is based on the server hardware type. You can change the contact list import rate by logging in to the Cisco Unified IM and Presence Administration user interface and choosing System > Service Parameters > Cisco Bulk Provisioning Service, then change the variable under Import Users Contact Rate. However, if you increase the default import rate, this results in a higher CPU and Memory usage on IM and Presence Service.

After you provision the Skype for Business/Lync/OCS users on Cisco Unified Communications Manager and license them for IM and Presence Service and an IM and Presence Service supported client, you can install the client software on the users’ desktops. See Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager for information about deploying IM and Presence Service supported clients.

Before migrating users from Skype for Business/Lync/OCS to IM and Presence Service, Cisco recommends that you set the Maximum Contact List Size and Maximum Watchers settings on IM and Presence Service to unlimited. This ensures that each migrated user contact list is fully imported to IM and Presence Service.

After all users have been migrated to IM and Presence Service, reset the Maximum Contact List Size and Maximum Watchers settings on IM and Presence Service to the desired values. The system default value is 200 for Maximum Contact List Size and 200 for Maximum Watchers size.

Note	If you are performing a phased migration of users from the Microsoft server to IM and Presence Service, do not reset the Maximum Contact List Size and Maximum Watchers values until all users have been migrated.

The following procedure describes how to set values for the Maximum Contact List Size and Maximum Watchers settings.

Note	If you have a multicluster deployment, you must perform this procedure on each cluster. When you change Presence settings, they are applied to all nodes in the cluster; therefore you need to set them only on the IM and Presence Service publisher node within any given cluster.