Office 365 / SharePoint – Migrate your On Premises SharePoint content to SharePoint 2010 Online – Part 1 – Migration tool installation

Once you have decided to go to Office 365 and use SharePoint Online, you may want to migrate your content currently hosted on On Premises SharePoint environment.

This migration can’t usually be done without third party tool, except if you want to move everything manually Smile.

This post will cover the SharePoint content migration to Office 365 using AvePoint DocManager tool; this doesn’t cover important preparation work such as identity the content to be migrated, check custom development…

Migration tool installation

The first thing is to install the migration tool. You don’t have to install it on a SharePoint server; SharePoint access will be done through an agent deployed on SharePoint servers.

Run the setup program and follow the wizard; there is almost nothing specific: accept EULA, enter name and organization name… I’ll just show you what is important.

Define the installation location


Select the installation options:

  • Completed: will install all DocAve service on the server
  • Advanced: allow to define what service will be available on the server

Control Service: used to manage all operations performed with DocAve. All agent (deployed on SharePoint server) will use this service to communicate with the manager

Media Service: used to manage data storage used and managed through DocAve, including disk space used for backup operations

Report Service: used by the report service to report SharePoint usage reports (site collections, users, features…)


Once you have defined the installation options, the setup is checking if prerequisites are meet before starting the installation.


Next steps depend of your installation option, if you selected Completed installation all steps will be done, else only the one related to your installation option.

Control Service

DocAve is using an IIS web site to be used so you have to define the settings for the new IIS site (server and communication) as well to create a new application pool. This will be used by the Control Service where DocAve agents will connect.


Then, you have to define the SQL server used to store configuration; in case of the database doesn’t exist, the installation will inform you and ask to confirm the database creation. You can also decide to install SQL Express provided with DocAve – off course, this is not recommended for production use.


Media Service

You just have to define the server running the Control service and access to the media service (server and communication port).


Report Service

It’s almost the same configuration type than Media service but you will have to define a SQL server for the report and auditor databases; you can automatically reuse previous SQL settings.



At the end of the installation a passphrase is generated, please note it as you will need later when you will deploy your agent.

Deploy DocAve agent

Run the setup program for DocAve agent on your SharePoint servers to be managed using DocAve.

There is nothing specific to do here except you have to define the communication settings with Control service; don’t forget you may have to define exception on firewalls to allow communication between the agent and the Control service.


Then you have to enter the passphrase generated during DocAve installation and a service user account to run the DocAve agent service.


On my next post we will see how to connect to Office 365 and prepare the
migration from On Premises to Office 365.

Leave a Comment

Your email address will not be published. Required fields are marked *