Skip to main content

Allotting Time for Cloud Migration




When planning your cloud migration, don't forget to allow time to move the data from your current provider to the cloud provider.  Email and document management systems grow significantly over the years, and your data may take longer to move than you think, even if everything goes smoothly.

We clocked these benchmarks on a recent migration:

Duration and Speed - Exchange on-premise to Office 365
Statistic
Source
Destination
Active Duration
4 hours
a day
Passive Duration
a day
2 hours
Data Speed
2,453.15 MB/hr
364.72 MB/hr
Item Speed
29,620 items/hr
4,404 items/hr


Duration and Speed - IMAP to Office 365


Statistic
Source
Destination
Active Duration
3 hours
8 hours
Passive Duration
5 hours
an hour
Data Speed
2,593.17 MB/hr
1,093.70 MB/hr
Item Speed
9,666 items/hr
4,071 items/hr

Many factors go into the speed of the migration, such as the speed of all network connections you are using and the underlying hardware and network performance for on premises implementations.

You also should consider the time devoted to monitoring the migration and restarting failed processes.

Some cloud providers offer shortcuts to migration which allow you to send hard drives to their facilities to eliminate the Internet performance bottleneck, but this requires advance planning and coordination, especially if you do not want to have the systems run in parallel.

Migration tools provided by cloud vendors and third parties can simplify your work, but at the end of the day the data needs to move from one place to another, and this inevitably takes time.























Popular posts from this blog

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun