Mover 雲端移轉Mover Cloud Migration

簡介Introduction

我們的目標是在各種無法完美共同作業的 Web 技術之間充當媒介。Our purpose is to act as an intermediary between various web technologies that don't play nice together. 我們將您的檔案從某位置複製到另一個位置。We take your files from one place and copy them to another. 無須下載,也無須監視,我們的 Web 主控應用程式能完成所有工作!No downloads and nothing to watch over—our web-hosted app does all the work!

進行任何公司移轉都是一項艱鉅的工作。Undertaking any corporate migration is a daunting task. 將資料移至雲端時,有許多需要考慮的事項。When moving your data to the cloud, there are many things to consider.

檔案處理摘要File processing summary

傳輸檔案時,會從 Office 365 下載一份臨時副本到暫時伺服器,並將它上傳到 Office 365。When we transfer a file, a temporary copy is downloaded from Office 365 to a temporary server and then uploaded to Office 365. 成功上傳時,該檔案會從暫時伺服器中刪除。Upon successful upload, that file is deleted from the temporary server. 移轉完成時,該暫時伺服器就會終結。When your migration is complete, that temporary server is destroyed. 任何記錄資料都會在 90 天內過期,我們不會保留。Any log data expires in 90 days and is never retained by us. 除了複製檔案和資料夾及共用權限以外,我們不會執行任何動作。We do not perform any actions beyond copying files and folders and sharing permissions. 我們永遠不會執行刪除作業。We never perform delete operations.

與專案關係人溝通Communicating with stakeholders

移轉對任何組織來說都是重大工作。A migration is a significant undertaking for any organization. 嘗試掌握所有資料並與員工溝通是相當複雜的過程。Trying to grasp the entire extent of all data and communicating with your employees is complicated. 我們能理解!We sympathize!

在移轉前、移轉期間及移轉後與使用者清楚有效地溝通是非常重要的。Before, during, and after a migration, it is critical to communicate clearly and effectively with your user base. 我們為您的轉換小組提供及時的支援和通訊材料,以協助您與每位專案關係人溝通這些變更。We provide timely support and communication materials to your transition team to help you communicate these changes with each stakeholder.

管理層級 - 管理層級需要移轉方式和原因的簡潔資訊,例如成本、優點和期待。Management — Management needs succinct info about the how’s and why’s of the migration, such as costs, benefits, and expectations. 您必須以清楚的方式呈現成功移轉後的情況。You must paint a clear picture about what a successful migration should look like. 部門運作時,細微的資訊十分重要。Granular info is important when running a department.

例如,銷售經理需要知道作業會如何受到影響,假設 員工是否仍可視需要在週末加班?For example, the Sales Manager needs to know how operations will be affected, such as Can employees still work over the weekend, if needed?

使用者 - 使用者是您的基本員工。Users — These are your bread-and-butter employees. 他們必須知道何時會發生變更,以及負責回答疑問或問題的對象。They need to know when changes are taking place and who to go to with questions or issues.

要處理的主要問題:Key questions to address:

  • 我們為什麼要移轉資料?Why are we migrating our data?
  • 這對我有何影響?How does it impact me?
  • 有哪些優點?What are the benefits?
  • 這項變更會有什麼影響?How disruptive is this change going to be?

協力廠商 - 如果組織外的人員有在文件上共同作業的存取權,這可能會因而造成中斷且需要再次共用資料。Third parties — If people outside your organization have access to collaborate on documents, this could potentially be interrupted and require resharing of data. 我們會在本指南中說明此活動的最佳做法。We describe best practices for this event in our guide.

IT 技術服務人員/支援人員 - 如果貴組織的規模足以讓其他員工擁有特定支援人員,這些人員必須了解每個移轉步驟。IT Helpdesk/Support staff — If your organization is large enough to have specific support staff for other employees, they must understand each step of the migration.

規劃Planning

規劃是移轉最艱難的一部分。Planning is the most difficult part of a migration. 要得到正確的結果,這也是最重要的階段之一。It is also one of the most critical phases to get correct. 若要順暢且無壓力地移轉,您必須收集相關的組織資訊、決定專案時間表,並緩解可能出現的任何意外。To have a smooth and stress-free migration, you must gather relevant organizational info, determine project timelines, and mitigate any surprises that may appear.

收集資訊Gathering info

移轉前,請務必收集順利執行移轉所需的所有資訊。Before migration, it is important to gather all the info you need to run the migration smoothly. 請確定您已核對下列檢查清單中的資訊。Make sure you have confirmed the info from the following checklist.

移轉資訊檢查清單Migration info checklist

  • 要移轉的使用者人數Number of users to migrate
  • 資料擁有權Data ownership
  • 資料分佈Data distribution
  • 要移動的資料量Amount of data to move
  • 要移動的檔案數目Number of files to move
  • 個別檔案大小和/或平均檔案大小Individual file sizes and/or file sizes on average
  • 您的移轉小組是誰?Who is your migration team?
  • 您與我們聯繫的指定連絡人是誰?Who is your designated contact with us?
  • 我們與您聯繫的連絡人是誰?Who is our point of contact with you?

掃描Scanning

為了協助您規劃,我們提供掃描功能。To help with your planning, we offer a scanning feature. 我們的掃描會識別多少使用者擁有資料,以及要移動的資料量。Our scan identifies how many users own data and how much there is to move.

此掃描實際上是未設定目的地的模擬試執行移轉,可協助您在開始移轉資料前找出任何有問題的檔案/資料夾。This scan is effectively a simulated dry-run migration, with no set destination, which helps to identify any problematic files/folders before you begin migrating data.

注意

首次設定移轉後,[移轉管理員] 便提供掃描功能。The scan is available in our Migration Manager after you have first set up a migration.

請參閱本指南以進一步了解完整的移轉程序,或直接跳到 設定移轉Read through this guide to better understand the full migration process, or skip ahead to Setting Up the Migration. 如需如何執行掃描的詳細指示,請參閱 掃描For detailed instructions about how to run the scan, see Scanning. 另請參閱執行 Mover 移轉See also Running the Mover migration

要移轉的使用者人數Number of users to migrate

每位 使用者 都是由唯一來源和目的地配對所定義。Each user is defined by a unique source and destination pairing.

例如:For example:

  • user01@example.com => user02@example.comuser01@example.com => user02@example.com
  • user01@example.com => user03@example.comuser01@example.com => user03@example.com

這些會被視為兩個不同的 使用者授權,因為是不同的目的地。These would be considered two separate user licenses because they have different destinations.

Mover 會自動調整您的傳輸並行處理量。Mover automatically scales your transfer concurrency up and down.

資料分佈Data distribution

由於我們會以高度平行的方式複製資料,而且我們的伺服器會根據各雲端儲存空間提供者可處理的速度盡快傳輸資料,因此決定所有使用者的資料分配是移轉的極重要元素。Determining the distribution of data across the user base is an extremely important component of a migration because we copy data in a highly parallel manner, and our servers transfer data as fast as each cloud storage provider can handle. Office 365 對下載及上傳的資料速度有費率限制。Office 365 has rate limits for how fast data can be downloaded and uploaded.

同時傳輸的使用者越多,您的移轉輸送量就越高。The more users simultaneously being transferred, the higher our throughput for your migration. 強烈建議您將大型資料集的使用者分成較小的帳戶,以便更快傳輸。We highly recommend that users with very large data sets be broken into smaller accounts to facilitate faster transfers.

注意

為了最大化輸送量,使用者不應擁有超過 5TB 的資料。To maximize throughput, users should not own greater than 5TB of data. 您擁有的使用者越多,且使用者擁有的資料量越小,您的移轉速度就越快。The more users you have, and the smaller the amounts of data they own, the faster your migration proceeds.

例如:For example:

  • 如果某使用者擁有 10 TB 的資料,我們建議您將這些資料分給 10 位使用者,讓每位使用者擁有 1 TB 的資料。If one user owns 10 TB of data, we recommend dividing that between 10 users so that each one owns 1 TB.

如果資料無法分割,這也不會妨礙其他使用者進行移轉。If data cannot be broken up, this should not hinder other users from migrating. 一般來說,具有大量資料的使用者需要大量時間來移轉。As a general rule, users with a lot of data require a lot of time to migrate.

要移動的資料量Amount of data to move

了解要移動的資料總量有助於為移轉建立更實際的時間表。Knowing the total volume of data you are moving helps to create a more realistic timeline for your migration.

您的移轉小組Your migration team

建立移轉小組,以領導組織完成專案。Establish a migration team to lead your organization through the project. 小組的角色包括在移轉程序中與我們連絡、進行訓練,並通知員工各項變更。The team’s role includes liaising with us, undergoing training, and notifying employees of each change during the migration process.

IT 經理或 IT 主管是做為連絡人的最佳選擇,因為他們了解貴組織系統的內外結構。An IT Manager or the Head of IT is a good choice for our point of contact because they understand the ins and outs of your organization's systems. 為了確保順利成功移轉,我們將密切共同合作,並在每個步驟中協助您。To ensure a smooth, successful migration, we work closely together and are with you every step of the way.

時間表Timelines

符合現實Be realistic

規劃、執行及完成移轉所需的時間取決於許多因素。The amount of time required to plan, execute, and wrap up a migration depends on many factors. 組織需求、預算、安全性審查及管理支援只是其中幾個。Organizational requirements, budget, security reviews, and support from management are just a few.

通常企業傳輸至少需要 30 天的時間來規劃及執行。We typically see corporate transfers take a minimum of 30 days to plan and execute. 請確定您在每個階段分配足夠的時間,我們稍後將在本指南中說明。Ensure you allot yourself enough time for each stage, which we cover later on in this guide.

評估您的使用者Evaluate your user base

計劃要移轉的使用者和移轉時間非常重要。It is critical that you plan which users are migrating and when. 請考慮以下問題:Ask yourself questions like these:

  • 要移轉整個組織,還是只移轉幾位使用者?Is the entire organization migrating, or just a few users?
  • 是一次移轉所有人,還是分割成部門、辦公室或地區來批次移轉?如果是這樣,原因為何?Is everyone migrating at once, or are you splitting them into batches like department, office, or region? If so, why?

注意

以這種批次移轉方式會增加移轉的複雜性和規模。Batching migrations this way increases complication, and may extend your migration.

建議您在組織較不忙碌的期間 (例如週末) 進行移轉,以避免工作中斷。We recommend migrating during a slower organizational period, such as the weekend, to avoid work interruptions.

持續使用您的帳戶Keep your accounts active

從 Office 365 移轉到 Office 365 時,請確保您所有的使用者皆為作用中且可存取。When migrating from Office 365 to Office 365, you need to ensure all your users are active and accessible. 了解您的 Office 365 可能會關閉或過期的時間,是安全地規劃足夠時間以進行移轉的關鍵。Knowing exactly when your Office 365 may shut down or expire is key to safely planning enough time to migrate.

考慮移轉速度因素Consider migration speed factors

我們是移轉資料最快的方式,但您的移轉速度仍可能受到瓶頸影響。We're the fastest way to migrate your data, but the speed of your migration may still be affected by bottlenecks. 速度瓶頸包含但不限於下列項目:Speed bottlenecks include, but aren't limited to, the following:

  • 要移動的檔案和資料夾數目Number of files and folders being moved
    • 客觀來說,這是網際網路的速度上限,因為這會決定所需的作業總數。This is objectively the biggest speed limit on the Internet, as it determines the total number of operations required. 大部分提供者的費率會限制每位使用者每秒對一個檔案的輸入。Most providers rate limit their ingress to one file per second per user. 這並非普遍適用,但卻是在預估時可使用的基準保守衡量標準。This isn't universally true, but it's a baseline conservative metric you can use when estimating.
    • 我們的客戶可觀察的平均是 2.4 MB 平均檔案大小。Our observable average across our customers is a 2.4 MB average file size.
    • 知道檔案大小才能預估傳輸速率。Knowing file size is necessary to estimate transfer speed. 如果您無法判斷正確的數目,大部分的服務皆可提供說明個別或平均檔案大小的報告。If you are not able to determine exact numbers, most services can provide reports that illustrate individual or average file size.
  • 移動的資料總量。Total amount of data being moved.
    • 資料總數可能會影響速度,但最終會由檔案數量決定。Total data can affect speed, but it is ultimately overshadowed by the number of files.
  • 使用來源或目的地 連接器 的伺服器連線。Server connections with the source or destination Connector.
  • 權限或共用配置的複雜度 (如果適用)。Complexity of permissions or sharing schemes, if applicable.

令人驚訝的是,除了要移動的資料大小以外,還有一個很大的影響因素。What may be surprising is how large of an impact factors other than the size of the data you are moving can have.

例如每個移動的檔案通常有多 0.5 秒的額外負荷。For example, it is common for there to be half a second of overhead per file being moved. 如果您要移動 200,000 個檔案,就將會有 200,000 秒或超過 2 天的額外負荷!If you are moving 200,000 files, this would be 200,000 seconds or more than two days' worth of overhead alone!

我們可以說無法確實告訴您時間的確切估計,因為在任何指定點上都有太多未知因素。Suffice to say, we cannot give you exact estimates on time because there are too many factors at play at any given point. 在您閱讀完本章節的時間內,我們早就可以輕鬆複製總量為多個 GB 的檔案,或同等於少量資料的數百件檔案。By the time you have read this section, we could have easily copied several files totaling many GB, or a few hundred files equaling a small amount of data.

我們隨時可與您進行關於估計的討論。We are available to have a conversation with you about estimates.

通知專案關係人有關移轉的資訊Notify stakeholders about the migration

您的員工對其資料有不同的需求,而了解他們的需要也十分重要。Your employees have different needs with respect to their data, and it is paramount to know what those are. 取得所有部門的購物清單、與經理聯繫,並識別其流程和應用程式的主要顧慮。Take a shopping list of all departments, contact their managers, and identify key concerns in their processes and apps.

請記住,雖然雲端儲存空間有時只是檔案容器,但使用者也可能會將雲端儲存空間用於協力廠商應用程式或進行更高級的共同作業。Keep in mind that while cloud storage is sometimes just a container for files, people might also be using it with third-party apps or for more advanced collaboration.

要傳送的電子郵件範例Example emails to send

主旨:注意:從 Office 365 移轉到 Office 365 的決定Subject: ATTENTION: Decision to Migrate from Office 365 to Office 365

郵件:幾個月前,管理層級決定我們會離開 Office 365,並移轉至新的 Office 365 網域。Message: A few months ago, management decided we will leaving Office 365 and transition to a new Office 365 domain. 在新版 Office 365 中,所有員工都能存取雲端儲存空間及其包含的應用程式。In the new Office 365, all employees will have access to cloud storage and its included apps.

我們會管理移轉,以確保我們的所有資料都能安全並有效地傳輸。We will manage the migration to ensure all of our data gets transferred securely and efficiently. 如果您有任何關於此程序的問題或顧慮,請與我們聯繫。If you have any questions or concerns about the process, let me know.

主旨:注意:有關雲端資料移轉的重要資訊Subject: ATTENTION: Important Info Regarding Cloud Data Migration

郵件:如您之前的電子郵件所述,我們將由 Office 365 移轉至新的 Office 365 網域,新的網域將成為我們的雲端儲存空間提供者。Message: As you know from prior emails, we are moving from Office 365 to a new Office 365 domain as our cloud storage provider.

為了協助進行此移轉,我們要求所有員工在太平洋時間 2020 年 4 月 7 日 17:00 完成工作,並將所有最後變更上傳至來源 Office 365 中的檔案。To assist in this migration, we ask all employees to finish working and upload any last changes to files in the source Office 365 by 17:00 PT on Friday, April 7, 2020. 在此時間之後,來源 Office 365 中的檔案或資料變更將不會移動。Changes to files or data in the source Office 365 after this time will not be moved.

在 2020 年 4 月 10 日,所有員工都會使用新的 Office 365 網域。On Monday, April 10, 2020, all employees will be using our new Office 365 domain.

您可以透過一般的管道,向直屬經理和/或我們的技術支援人員詢問問題與提出考量。Questions and concerns can be directed to your immediate manager and/or our technical support staff via the usual channels.