On-premises Public Folders Migration — Exchange Server Data Move

IT Partner’s On-premises Public Folders Migration service helps organizations move Microsoft Exchange public folders from one on-premises Exchange server to another. The service covers planning, migration execution, verification, and post-migration tasks for shared public folder content such as calendars, contacts, documents, and other public folder data.

The service is designed to migrate Microsoft Exchange public folder content, including shared calendars, contacts, documents, and other data stored in public folders. IT Partner verifies that the migrated public folders function as expected in the target on-premises Exchange environment.

No, this service is specifically scoped for migrating Microsoft Exchange public folders from one on-premises Exchange server to another on-premises Exchange server. If you need a cloud migration to Microsoft 365 or Exchange Online, confirm the appropriate service scope with IT Partner.

IT Partner defines the best migration method based on the customer’s requirements and Exchange environment. Possible methods include exporting and importing public folders using PST files, replicating public folder data from the source server to the target server, or using a third-party migration tool.

IT Partner selects the migration method after assessing the source environment, public folder hierarchy, data volume, network bandwidth, and required migration time frame. The right approach depends on those factors because public folder size, structure, and connectivity can significantly affect migration performance and risk.

The service includes defining the migration method, assessing the source environment, preparing and controlling the migration, verifying migrated data, performing necessary post-migration tasks, providing post-migration support, and completing follow-up or closure conversations. It is focused on moving public folder data and validating that it works in the new on-premises Exchange environment.

The service does not include informing users about upcoming changes, customer team training, or desktop software settings. Customer team training may be added as an additional service if required, but it is not part of the standard scope.

The stated service duration is 7 days. The exact migration schedule should be confirmed with IT Partner because the migration method, public folder data volume, hierarchy complexity, network bandwidth, and customer availability can affect timing.

The listed price for IT Partner’s On-premises Public Folders Migration service is $114 per GB. Because the service is priced by data volume, the final cost depends on the amount of public folder data to be migrated.

The engagement typically includes kickoff, migration discovery and planning, source environment preparation, target environment preparation, migration testing, migration execution, migration completion and source decommissioning, post-migration support, and follow-up closure. These milestones are used to assess the environment, choose the migration approach, move the data, and confirm the migration was successful.

IT Partner assesses the source Exchange environment to determine the migration scope and identify issues that could affect the migration. This includes understanding the public folder hierarchy, the migration method needed, and the timeline required for the customer’s environment.

IT Partner recommends using a dedicated network connection for the migration process to reduce the risk of network congestion. The migration account must also have appropriate permissions to read, write, modify, access, and migrate the public folder data.

IT Partner is responsible for defining the best migration method, assessing the source environment, starting and controlling the public folders migration, verifying successful data migration, and performing necessary post-migration tasks. IT Partner also provides post-migration support and participates in follow-up and closure conversations.

The client must provide a dedicated point of contact, coordinate outside vendor resources and schedules, and provide temporary access to the existing environment and IT infrastructure. The client is also responsible for configuring network equipment such as load balancers, routers, firewalls, and switches, making required DNS changes, and informing users about upcoming changes.

Yes, one of the success criteria is that end users can access public folders in the new environment using the same tools and interfaces they used in the old environment. IT Partner verifies that public folders function as expected after migration.

The service’s success criteria state that all public folder data should be migrated without loss or corruption, and IT Partner verifies that the data has been successfully migrated. As with any migration, the exact risk profile depends on the environment, data condition, migration method, and preparation, so any special risk concerns should be reviewed with IT Partner during planning.

The service description does not specify a guaranteed downtime window or exact business impact. Business impact depends on the selected migration method, data volume, public folder usage, network bandwidth, and cutover approach, so downtime expectations should be confirmed with IT Partner during migration discovery and planning.

Yes, the implementation plan includes migration testing in a test environment to confirm that the process works correctly and to identify issues before execution. This helps reduce migration risk because the chosen method can be validated before public folder data is copied to the target server.

After the migration, IT Partner verifies that the data was successfully migrated, performs necessary post-migration tasks, provides post-migration support, and completes follow-up or closure conversations. The implementation plan also includes source decommissioning after the migration is confirmed successful.

The implementation plan includes migration completion and source decommissioning once the migration is confirmed successful. Any specific decommissioning steps, dependencies, or customer change-control requirements should be confirmed with IT Partner before execution.