背景信息
阿里云携手 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.