Are you considering a public folder migration to Moss? One of the first requirements unit to fulfill is to get a deployer for Moss migration. You will undoubtedly come across quite a few providers for the tools you need and may even be overwhelmed with various offers. The responsibility of choosing a provider suitable for your requirements may become a challenging task unless you are prepared to conduct some research to understand which deployer you should be using.
You should be considering a provider who has all the knowledge needed for exchanging public folders. The deployer must enable content to migration to products from SharePoint and technology. The tool chosen should have been developed specifically to respond to the online migration requirements of moss, SharePoint 2007, SharePoint 2010, SharePoint 2013, and SharePoint 2016. The solution will allow the user to execute the export command from one workstation even as it loads the data on another. As the users will have the ability to connect remotely to the exchange server they can easily choose the content which needs to be migrated.
Using the Tzunami deployer for public folder migration to Moss is advised because this deployer for an exchange of public folders provides users the ability to export various types of objects from Exchange public folders to Moss. The type of folders which can be migrated include the following:
Mail items.
Calendars and appointments including recurring events.
Distribution lists and contacts.
Posts.
Tasks.
Documents.
Notes.
This provider is willing to offer support for additional object types if needed by its clients when contacted for the same.
During the process of export for the exchange public folders the Tzunami deployer exports the users and groups along with permissions which are mentioned below:
Read items, create items, create subfolders, edit own, edit all, owner, contact, visible, delete own, and delete all.
The users can perform the migration of user groups along with memberships and permissions by using the security mappings of Tzunami deployer even across domains of active directory.
Events located in calendars are exported along with their recurrence information. When such events are migrated to a calendar list in SharePoint the events in the SharePoint will begin to have the same recurrence information.
Depending on the usage you have planned for your SharePoint the mail items can be migrated as MSG files into a library of documents but you will either need Microsoft Outlook or something similar to open the documents. The data items will be in a generic list and the attachments in the mail will appear as attachments of the data item. The body of the mail is migrated as a property of the items. It must be noted that during the process of export the attachments of mail items are migrated both as a part of the MSG file of the mail as well as any regular items it may carry. This gives users an opportunity to migrate items in the mail is as a document library or a generic list.
Users considering a public folder migration to Moss are suggested to conduct plenty of research to understand the appropriate tool they should be using for the migration. A large number of providers competing between themselves to market the deployer’s they have developed users may receive a number of offers when they submit an inquiry for the deployer. They may even be tempted with low prices which is a common technique used by most companies to attract fresh clients.
It is essential for users only to deal with companies such as Tzunami because this is a market leader in the business of providing deployer’s for the migration of exchange public folders and will be suitable for the needs of the users even when they decide on Moss migration.