MacroView Migrate can migrate files and folders from the file system or Outlook into SharePoint. It traverses the source folder structure and invokes a workflow against each file and folder that determines the destination. This means a folder structure can be transformed into a SharePoint hierarchy of sites, libraries, folders and document sets.
MacroView Migration works best when the target structure is pre-provisioned by MacroView Solution Provisioning (MVSP) however this is not required and structure can be provisioned as part of the migration workflow.
MacroView Migrate installs to: %LocalAppData%\MacroView\MigrationTool
The MSI does not require administrator privileges and only writes files to the above path. This means the MSI must be installed by each user that intends to use it.
After installation the application can be launched from the Windows Start menu:
If you are licensed to use MacroView Migrate, you can download it from here MacroView Migrate Download
If you do not have a license or cannot access to the above page, contact firstname.lastname@example.org
The MacroView Migrate user interface is built around the concept of having a series of migration 'packages' with each defining a source, destination, workflow and other settings. When using the application for the first time a window similar to the following is displayed:
Right-click on a package and select Edit Package. The Migration Package window is displayed:
- The Name identifies the migration package. This can be any value and is only used for identification purposes.
- The Source type determines whether the migration package will migrate from the file system or from Outlook.
- Use the Source location ellipsis button to select a location to migrate from. If File System is selected then the Windows folder picker dialog is displayed. If Outlook Store is selected then the Outlook folder picker is displayed. Note that Outlook must be running under the same user account in order for the picker to be displayed.
- Enter a SharePoint URL as the Destination path. This must be a valid Uri and should be site, library or folder path. The Destination path will determine how the migration workflow is structured.
- Check License will confirm whether or not your copy of MacroView Migrate is licensed. The un-licensed trial version will only process the first 1000 items in a workflow. To obtain a licensed version of MacroView Migrate contact Services@macrview.com.au
A migration package won't migrate anything without a workflow. The workflow determines the logic that applies to each file and folder that is processed in the source location, such that the item is either migrated or ignored. If the item is to be migrated the workflow also specifies a provision activity which determines the SharePoint object that should be created for the source item.
Click the Workflow... button to see the workflow:
This displays the Workflow Designer window which contains a re-hosted Workflow Foundation 4.5 designer. As mentioned, the workflow is invoked for each source file and folder so should be designed with this in mind.
The default workflow will allow you to migrate folders and files or emails and reproduce the same folder structure in SharePoint.
For assistance in creating a custom workflows contact Macroview at Services@macroview.com.au and one of our solution consultants will be able to help you.
The Settings tab 0n the Package window contains various options that are used when running the migration package:
|Include source location||Processes files in the source location folder|
|Ignore hidden source items||Ignores items that are hidden on the file system|
|Maintain created and modified dates||Retains source created and modified dates when files and folders are created in SharePoint|
|Trim invalid file and folder name characters||Removes any characters that are invalid in SharePoint from file and folder names|
|Create file copy if found in destination||Uploads files with a 'copy' suffix appended to their names if a file with the same name already exists in the destination|
|Standardize message file names||Uses the default MacroView DMF / Message email naming convention when uploading MSG and EML files|
|Extract Zip files in source root||Traverses the content of Zip files in the source location root folder (if included) and migrates the contained folders and files as if they existed on the file system in the source location|
|Email save format||Specifies the format to use when saving items from an Outlook Store source|
|Convert files to email save format||Converts MSG or EML files from a file system source to the email save format|
|Skip item discovery||Prevents additional checks that allow the progress indicator to show the percentage complete but slow the migration process. Once initial test runs are complete it is recommended this is checked for larger production runs.|
|Run validates source items only||Evaluates the workflow for each item in the source location but does not perform any actual migration. Useful for verifying that the workflow captures the expected items.|
Run a Migration
Once a migration package is ready to go, right click it and select Run:
This will immediately begin processing and, if required, display an authentication dialog to allow the user to sign in to the destination SharePoint server. A progress dialog is then displayed:
Clicking Cancel or dismissing the progress dialog will immediately cancel the migration operation.
When complete, click Done
Check Migration Results
Once a migration in complete, results are available on the migration package History tab:
Double click a row to open the selected results. For large result sets, right-click and Export to CSV:
Creating Migration Packages
To create a new Migration Package, right-click anywhere in the Migration Package Window and select New...
Then select the type of package you want and click Create
You will then be presented The Migration Package window.
You can also clone, export and import migration packages.
To clone an existing migration package, right-click the package and select Clone
To export a migration package to the file system, right-click on the package and select Export then provide a filename and select a save location.
To import a migration package from the file system, right-click in the Migration packages window and select Import, then select the package file.
You can also import and export just the workflow component of a migration package by opening its Workflow Package window and right clicking on the Workflow... button
An application error log is written to: %LocalAppData%\MacroView\MigrationTool\Logs
This log contains details of any exceptions that occur outside of a migration operation. When running a migration package, refer to the package history for any errors that occur when processing items or provisioning objects in SharePoint.