背景信息
阿里云攜手 Salesforce，已將 Customer 360 引入中國。阿里云上的 Salesforce 包含兩個部分：
Salesforce Connected Experiences Gateway（互聯網關CXG），專為中國打造的本地化擴展組件
Salesforce 的全球核心產品，包括銷售云、服務云和平臺云
成功遷移到阿里云上的 Salesforce 并不是“直接遷移”那么簡單。這需要完成一個端到端的遷移項目。此數據手冊旨在幫助您簡要了解這種遷移項目的主要內容，并為其做好充分準備。
若要訪問完整的《技術遷移指南》（共 30 頁），請聯系您的銷售代表。
阿里云上的 Salesforce 遷移過程
您的端到端遷移過程可能包含四個步驟：
遷移準備工作
每一位客戶的 Salesforce 組織都有自己的獨特之處。您可能有一個使用了十余年的全球共享組織，由包括中國在內的等多個地區使用，可能有為中國用戶專設的組織，也可能根本沒有供中國使用的 Salesforce 組織。您需要了解Salesforce 現有組織環境，從而確定通過哪種遷移方法能在阿里云上的 Salesforce 中構建預期實例。
準備階段的預期結果為：
了解您的 Salesforce 現有組織環境
了解阿里云上的 Salesforce 遷移選項
就元數據/數據遷移方法達成共識
就現有全球 Salesforce 實例與阿里云上的 Salesforce 實例之間的關系和數據同步范圍達成共識
為實現預期，需要請以下利益相關者參與：
內部——IT 團隊、Salesforce 架構團隊
外部——系統集成商（負責實現您當前的 Salesforce 組織）
您至少需要完成（不局限于）以下這些步驟：
確認您的 Salesforce 現有組織類型（全球共享、中國專用、或者沒有適用于中國的 Salesforce 組織）
召開研討會，根據現有組織類型確定首選元數據遷移方法
召開研討會，了解現有組織的數據歷史記錄，并就指定待遷移的中國相關數據的適當方法達成共識
在您決定將 Salesforce 組織遷移到阿里云上的 Salesforce 平臺之后，可以盡快啟動準備階段。您應考慮調查現有Salesforce 組織、所有利益相關者對遷移方法的看法，以及完成遷移預算審批流程所需的時間。
驗證遷移方法
阿里云上的 Salesforce 將盡可能與 Salesforce 全球版本保持一致，但也有一些不同之處，例如：
沒有 Einstein 服務，因為此服務需要跨境傳輸客戶數據
僅支持 Lightning，如果您現有的 Salesforce 組織仍使用 Classic，則需要先升級到 Lightning，然后才能遷移到阿里云上的 Salesforce
某些功能（如Omni Channel）在正式發布之初有可能無法使用
全球 Salesforce 組織中的 ISV 軟件包在中國可能無法使用
因此，需要明確指定并驗證元數據和數據的遷移范圍，并為那些不在遷移范圍內的功能制定對應策略。
驗證階段的預期結果為：
舉辦研討會，以確認并簽核元數據和中國相關數據的遷移范圍
確定并記錄主要阻礙，例如，在阿里云上的 Salesforce 正式發布時，Salesforce 現有組織尚未為升級到Lightning 做好準備，解決方案組件（營銷、商務、CPQ、FSL 等）或 ISV 軟件包尚未發布
與阿里云和 Salesforce 團隊，以及 SI 合作伙伴一同制定了對應策略（Lightning 升級、替代解決方案、變更管理）
與您選定的 Salesforce SI 一同全面測試并優化了遷移計劃
有一些工具可為您提供協助：
組織比較工具，可將您的現有組織與準備就緒的 Salesforce 組織進行比較，以確定需要遷移的初始自定義數據范圍
測試元數據和數據遷移流程的免費或商用工具
我們建議您在預期遷移項目開始日期前 3 個月內啟動驗證階段。
遷移到阿里云上的 Salesforce
雖然每位客戶的具體情況不同，但有幾條規則對于每一個遷移項目都很重要：
不要僅僅復制所有的內容并預期能夠正常運行。例如，某些標準字段可能不適用于阿里云上的 Salesforce 實例組織環境。在您的全球 Salesforce 組織中的特殊要求，有些標準或自定義字段可能已經超出了預設的字段長度限制。
在嘗試執行組織拆分任務時，如果無法確認某些元數據配置是否與中國范圍相關，請先選擇遷移它們。
在遷移過程中，可能會出現增量數據。提前做好應對計劃，或者直接聯系 Salesforce，在數據遷移過程中啟用“只讀”模式。
務必按特定順序導入對象數據，以保持記錄關系。例如，先導入父記錄后再導入子記錄，或是先導入必需字段記錄等。
遷移步驟：
了解并避開限制（請參閱 <Salesforce 限制>）
檢查遷移前核對清單：
自定義 Connected App 已準備就緒，可連接 SFDX 工具以進行遷移
沒有硬編碼的網址
啟用相關設置（多幣種、支持的語言、個人賬戶等）
按特殊請求添加系統限制（API、選取值、字段長度等）
禁用觸發流，避免出現意外的增量數據
按正確順序遷移元數據和數據
在導入前更新元數據，例如為新組織創建/更新用戶名/電子郵件，為某些中國相關數據導入新的自定義對象/字段
確定保持數據關系（父項/子項關系）的方法
處理各類特殊數據，如加密數據、審計數據、系統生成的數據等
了解哪些數據不能遷移（商機歷史記錄、字段歷史記錄等）
在阿里云上的 Salesforce 實例上添加 IP 允許列表的記錄以保證端點可以被訪問
測試和遷移后任務
我們一再強調，在遷移項目中進行全面合理的測試是非常重要的。我們深知，每個遷移項目都有著不同的范圍，我們可能無法考慮到所有情況，但完整版“技術遷移指南”提供了一份示例測試指南。請務必咨詢您的遷移團隊或認證解決《技術遷移指南》（共 30 頁），請聯系您的銷售代表。
測試階段的預期結果為：
您參考“技術遷移指南”制定了自己的測試計劃
您制定了遷移后異常處理計劃
已向內部利益相關者（全球 Salesforce 團隊、IT 團隊、中國業務部門用戶）傳達了變更
在驗證完畢后發送電子郵件，提醒最終用戶注意網址變化
對最終用戶的影響：提醒支持社區和領導團隊網址將發生變化，但書簽、Chatter 帖子中的鏈接、模板等將重定向到新實例
已執行測試并與內部和外部受影響方溝通，說明 Mydomain 將進行更改并且會影響其體驗云產品訪問鏈接
已（通過 Chatter 和電子郵件或您企業偏好的其他溝通方式）通知所有員工：阿里云上的 Salesforce應用程序已可供訪問，登錄網址已更改，且所有瀏覽器書簽都將重定向（前提是您遵循了我們的允許名單IP 地址最佳實踐）
傳達相似（或不同）的本地流程，并說明全球組織和本地組織之間的差異
本地內部團隊啟用完成
已制定未來計劃（增強、異常管理）
在此我們一如既往地，感謝您對阿里云上的 Salesforce 的支持！
請繼續閱讀我們的“中國架構指南”，進一步了解阿里云上的 Salesforce、產品戰略和路線圖、集成模式、IT 和數據管理及發布管理的運營實踐，以及本地實踐，包括卓越中心 (CoE)、合作伙伴生態系統及中國用戶體驗和采用。
Background Information
Alibaba Cloud has introduced Customer 360 to China in partnership with Salesforce. Salesforce on Alibaba Cloud consists of the following parts:
● Salesforce Connected Experiences Gateway (CXG), a localized extension component designed specifically for China
● Salesforce’s global core products including Sales Cloud, Service Cloud, and Salesforce Platform.
To successfully migrate to Salesforce on Alibaba Cloud is not a simple task like ‘lift - shift - land’. It is an end-to-end migration project. This data sheet is designed to help you understand and prepare for this migration project from a high level perspective.
To access the full the 30-page “Technical Migration Guide”, please reach out to your sales representative.
Salesforce on Alibaba Cloud Migration Journey
Your end-to-end migration journey may consist of four steps.
Prepare for Your Migration
Every customer’s Salesforce org is unique. You could have a global shared org that has been used for 10+ years including China usage, you could already have a dedicated org for users in China, or there could be no Salesforce org for China usage at all. You need to understand your As-Is Salesforce org environment to decide the migration approach of building your To-Be Salesforce on Alibaba Cloud instance.
At the preparation stage, the expected outcomes are to:
● Understand your Salesforce As-Is org environment
● Understand your Salesforce on Alibaba Cloud migration options
● Agree on the migration approach for metadata/data migration
● Agree on the relationship and data synchronization scope between your existing global Salesforce instance, and the Salesforce on Alibaba Cloud instance
To archive the expectations, the following stakeholders will need to be involved:
● Internal - IT team, Salesforce Architecture
● External - System Integrator (who implemented your current Salesforce org)
And below are the steps you are required, but not limited, to take:
● Confirm your As-Is Salesforce org types (global shared, dedicated, no Salesforce org for China)
● Workshop to decide your preferred method of metadata migration based on your existing org type
● Workshop to understand the data history in your As-Is org and agree on the appropriate method to define the China-related data for migration
You can start the preparation stage as soon as you have decided to migrate your Salesforce organization to Salesforce on Alibaba Cloud. You should consider the time to investigate your As-Is org, to align all the stakeholders on the migration approach, and to complete the migration budget approval process.
Validate Your Migration Approach
Salesforce on Alibaba Cloud will be as similar to the Salesforce global version as possible, with some differences, for example:
● No Einstein Service as this will require cross border customer data transfer
● Lightning support only. If your As-Is Salesforce org is still on Classic, you will need to upgrade to Lightning first before you can migrate to Salesforce on Alibaba Cloud
● Some features like Omni-Channel might not initially be available at the time of GA
● The ISV package in your global Salesforce org might not be available in China
Therefore, the migration scope for both metadata and data will need to be well defined and validated, and a mitigation plan created for those features which are out of the migration scope.
At the validation stage, the expected outcomes are:
● Workshops have been held to confirm and sign-off on the migration scope for metadata and China-related data
● Major blockers have been identified and documented, for example, the Salesforce As-Is org is not Lightning ready, the solution components (Marketing, Commerce, CPQ, FSL, etc), or the ISV packages are not yet available at the time the Salesforce on Alibaba Cloud instance becomes Generally Available
● A mitigation plan (Lightning upgrade, alternative solutions, change management) has been created with the Salesforce team and your SI partner
● The migration plan has been thoroughly tested and optimized together with your selected Salesforce SI
Some tools you can use to help:
● An org compare tool that compares your As-Is org with a clean Salesforce org to identify the initial scope of customizations to be migrated
● A free or commercial tool to test the metadata and data migration process
We recommend that you start the validation stage no later than 3 months before your targeted migration project start date.
Migrate to Your Salesforce on Alibaba Cloud Environment
Although each customer org is different, there are several rules that are important for every migration project:
Don’t just copy everything and assume it will work. e.g. some standard fields might not be available in the Salesforce on Alibaba Cloud instance org environment. And some standard or custom fields might exceed the length limit due to special requests in the past.
When you try to conduct the org split task, if some metadata configurations can not be confirmed if they are related or not related to China scope, MIGRATE THEM FIRST.
There might be incremental data during the migration. Plan ahead how to handle this situation, or simply contact Salesforce to enable the ‘read-only’ mode during data migration.
It's important to import object data in a particular order to maintain record relationships. For example,import the parent record before the child record, import the mandatory field record first,etc.
Migration Steps:
Understand and avoid the limitations. For more information, see Salesforce Limitations.
Run the pre-migration checklist:
? Custom connected app is ready to connect the SFDX tooling for migration
? No hard-coded URL
? Enable the relevant settings (multi-currency, supported languages, personal accounts, etc.)
? Apply the special request to increase the system limits (APIs, pickup values, field length, etc.)
? Disable the triggered flow to avoid unexpected incremental data
Migrate metadata and data in the right order
Update the metadata before import, like creating/updating username/email for new org, new custom object/field for some China-related data importing
Decide approach to maintain the data relationship (parent child)
Handle the special data like encrypted data, audit data, system generated data, etc.
Understand which data cannot be migrated (opportunity history, field history, etc.)
Add Preferred Alternatives to IP Allowlisting on Salesforce on Alibaba Cloud instance
Testing and Post-Migration Tasks
We cannot emphasize enough how important it is to have everything tested properly. While understanding that each migration project scope is unique and we may not cover every circumstance, we have provided a sample testing guide in the complete Technical Migration Guide for you to download.
Please make sure to consult your migration team or certified solutions for the "Technical Migration Guide" (30 pages). Please contact your sales representative.
At the testing stage, the expected outcomes are:
● You have built out your own test plan using the Technical Migration Guide as a reference
● You have made a plan to handle exceptions after migration
● Changes have been communicated to the internal stakeholders (Global Salesforce Team, IT team, China business users):
Sent email after verification is complete reminding end users about the change in the URL
End User Impact: Have reminded support community and leadership team that URL will change, but bookmarks, links in Chatter posts, templates, etc will redirect to the new instance
Have tested and communicated with internal and external impacted parties that Mydomain will be changed and it will impact your experience cloud
Have notified (Chatter & Email) all employees that: the Salesforce on Alibaba Cloud application is accessible, the login URL has changes, and all browser bookmarks will redirect (assuming you follow our best practices of whitelisting IP addresses)
Have communicated similar (or different) local process and differences between Global org and Local Org
● Local internal team enablement in complete
● A future plan (Enhancement, Exceptions Management) has been created
As always, thanks for your support on Salesforce on Alibaba Cloud!
Continue to read our China Architecture Guide to learn more about the Salesforce on Alibaba Cloud platform, product strategy and roadmap, integration patterns, the operations practices of IT and data governance and release management, and local practices including Center of Excellence (CoE), partner ecosystem and user experience and adoption in China.