SitesMove Documentation
Version .95
SitesMove allows you to migrate your existing content from Microsoft SharePoint to the Google Apps platform. Easily move a large number of files and documents to Google Apps Sites. SitesMove provides administrators a smooth transition to Google Apps.
Product Features
- Quickly transfer files and documents to Google Sites
- A powerful and easy to use graphic user interface
- Detailed reporting, logging and saving of configurations
Platform Requirements
- Windows Based PC (XP, Vista, Server) with .NET 3.5 Installed (Available through Windows Update or directly from MS)
- Google Apps Premier or Education Edition
- System Requirements (for .net 3.5)
- Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP
- Processor: 400 MHz Pentium processor or equivalent (Minimum); 1GHz Pentium processor or equivalent (Recommended)
- RAM: 96 MB (Minimum); 256 MB (Recommended)
- Hard Disk: Up to 500 MB of available space may be required
- CD or DVD Drive: Not required
- Display: 800 x 600, 256 colors (Minimum); 1024 x 768 high color, 32-bit (Recommended)
Tested On
- Windows XP Pro with .NET 3.5 Installed
- Google Apps Premier
Installation
The SitesMove utility is delivered via a Windows MSI Installer which includes product documentation. The provided installer package will add Start Menu items and entries under Add/Remove Programs.
Licensing
The SitesMove requires a license to be installed to be fully functional. Without a license file, the application will be in "Trial Mode", allowing you to perform only 5 move actions at a time. To obtain a license, please contact LTech for pricing.
Licenses should be placed in the application directory. The default location is: C:\Program Files\LTech\CloudMove\GUI
Configuration
Logging Setup
Logging for the SitesMove utility is handled using log4net.
Configuration options for log4net are stored in the application configuration file. Selecting different input modes for configuration keys in the SitesMove utility does not affect the configuration keys for log4net.
Below is the default configuration settings for log4net. The main configuration option that will be changed from the default setting is the log file location value (bolded). This can be a relative path or a fully qualified location on a drive or network share.
Changing the root level value will modify increase and decrease the amount of logging statements outputted, but may also omit useful logging information. It is not recommended to raise the value to "WARN" or above, as most logging statements are logged at the "INFO" level. Lowering the level to "DEBUG" will output logging statements indicating start and end points of methods.
For more information about configuring log4net see:
http://logging.apache.org/log4net/release/manual/configuration.html
Sample log4net Configuration
Output
The files selected are moved to the repository in the site mentioned in the configuration.
Windows Application Utility
The windows application utility is a graphic interface for the SitesMove utility. Configuration options are entered manually, but a configuration option is available as well that allows configuration options to be saved for future usage.
Configuration
Configuration is broken down into three separate sections on the main form.
Google Apps Credentials
- Domain - This is the source Google Apps domain to use for the export.
- Login - This is the user that will be used to query Google Apps for user information.
- Password - The user's password.
- Site Name - The name of the site where the files are to be moved.
Source Options
- SharePoint Instance
- Host URL: This is your sharepoint server's URL.
- User: The username on the sharepoint server.
- Password: The User's password.
- Domain: The domain on which the sharepoint instance is hosted.
- Admin Host URL: This is your sharepoint server's Admin Host URL.
- Temp Directory: This is the temp directory to aid the cloud move.
- Local Computer/Network
- Local Path: This is the local path where the files to be moved are placed.
- Recurse Folders: Check this if you desire all files in the subdirectories to be moved.
Repository
- Repository Name: The Name of the repository under which all the files are to be placed, if the repository does not exist then it will be created
- Date of backup
- Username
- User first name and last name
- Domain
- Number of successfully exported documents
- Number of documents unable to be exported
- Elapsed time
- Document format
- Spreadsheet format
- Presentation format
- List of successfully exported documents
- List of documents unable to be exported and reason per document
Executing Move
Once all required fields are entered the cloud move is ready to be ran. To run the utility you can click the 'Run' button that is placed along with the required fields.
If all parameters are valid, and the backup is started, all logging will be printed to the main text box on the 'Run' tab. At any point you can the output from the utility can be exported to a .txt file.
Reporting
The document backup utility supports reports for both users and domains. After completing processing, a user report is created that lists the following information:
User reports are stored under each user's folder, and are named report.txt.
Example User Report
Domain reports are available when processing the entire domain. They are not created when processing single users. Domain reports aggregate content from the user reports and provide a summary of the processing that was done for the domain.
LTech was able to provide us development expertise that we enjoyed working with. We were able to brainstorm well with them, good give and take, with solid professional recommendations from them.

