What is a Project?
A project is a collection of settings that defines how we communicate with the Source and Destination messaging systems. After configuring a project, you would then associate one or more items, like mailboxes.
The settings on a project include the following:
- The protocol that you wish to use to communicate with the Source and Destination servers (EWS, IMAP, POP, etc.).
- The server information used to connect to the Source and Destination servers (server names, server ports, etc.).
- For mailbox migrations, administrative credentials to access mailboxes. In most migration scenarios, the admin account needs to have full access rights to the Source mailboxes. Details for how to set this up can be found in the article Create an administrator account for login.
- Every setting on the project is applied to all mailboxes associated with that project.
- For settings that are represented as checkboxes, only selected settings are applied to the project. Not selecting a checkbox does not disable a selected setting inherited from the project.
Note: MSPComplete introduced the concept of endpoints. When creating a project, you should first create your endpoints within MSPComplete. See View, add, and edit customer endpoints.
|Project Type||Choose between a mailbox, public folder, document, archive, enterprise archive, cloud storage, collaboration, or database project. Note: you may not see all migration types in your list. The list of available project types depend on your access rights.|
|Project Name||A name you can use to identify the migration project.|
|Source||This is your Source server. Click on the edit icon (the pencil icon) to modify:|
I Know My Service Provider
|This option will assist in automatically populating fields, when migrating from or to hosted providers.|
|Choose the platform or type of server you are migrating from.|
|Depending on the server type selected, you will be prompted for the credentials necessary to gain access to the Source.|
|Destination||This is your Destination server. Click on the edit icon (the pencil icon) to modify:|
I Know My Service Provider
|Selecting this option will automatically populate fields.|
|Choose the platform or type of server you are migrating to.|
|Depending on the server type chosen, you will be prompted for the credentials necessary to gain access to the Destination.|
|Send successful migration email notifications to:||Allows you to specify users, including custom email addresses, to be notified by email upon successful migration.|
|Send failed migration email notification emails to:||Allows you to specify users, including custom email addresses, to be notified by email upon failed migration.|
|Customize Notification Emails||Allows you to create custom emails for migration success, migration failure, and requesting user credentials.|
|Number of days until an unused project is auto-deleted||Number of days in which the connector and all associated data are purged if not used. Purchase date is based on the connector create date, newest mailbox create date, or last mailbox migration complete date, whichever is the latest.|
|Filtering||Allows you to choose what items to migrate, depending on their date, or through more powerful custom filtering options.|
|Source/Destination Specific Information||Allows you to specify custom settings specific to the type of server you are migrating to or from.|
|Log subjects of failed items||Allows the system to log and display the subject of failed items.|
|Remigrate previously successful items||By default, we do not migrate items that were previously migrated, regardless of if they were removed from the Destination. Enable this flag to attempt migration of items that were removed from the Destination server but still exist on the Source.|
|Remigrate previously failed items||By default, we do not migrate items that we could not previously migrated after maximum retries when migrations are resubmitted. Enable this flag to attempt migration of items that previously failed to migrate.|
|Preferred data center||BitTitan is proud to offer data centers in several locations around the world. For best performance, choose the data center nearest your Destination sites.|
|Max. concurrent migrations||Maximum number of items that should be migrated at the same time. If more items are submitted than the specified limit, the other items will not begin until a running item completes or fails.|
|Max. errors per migration||Maximum failures that can be reached. If this limit is reached, the item migration is considered a failure and will stop. When the maximum failures have been reached, you should take corrective measures on the server corresponding to the errors and resubmit migration for continuation.|
|Do not retry errors||If an item fails to migrate, we will normally retry migrating the item several additional times before failing. Enabling this flag will result in no retries. Failure to migrate an item for any reason will be logged and skipped.|
|Support||Please contact support regarding the use of this field.|