B2C Commerce Realm Split FAQ

• When moving a site to a new realm, if that will be the first site in that realm, you will need to do the full Go Live process before we can mark that site live in the new realm. Please refer to Open a Go Live Ticket for B2C Commerce.
• You may need to move data over in multiple steps - Delta and the remaining entities should be exported based on how you would time the cutover.

• Basic Customer Profile
• Shipping Address
• Stores
• Payment Instruments (as outlined in How to export customer credit card data from Business Manager in B2C Commerce)
• Wish list
• Active Data

• Order HistoryOpen
• Orders in-stock pre/back ordered items

• Catalog
• Product Images
• Migration of URLs/title of images for existing products
• Content Assets associated with the product
• Product Swatch relationship

• Generic Content

• Coupons (see also section 17 if using system-generated codes)
• Customer Groups

• Categories
• Assigning products to categories
• Sorting
• Facets
• Recommendations/Cross Sell/Perfect Pairing

• Store set up

1. Notify the Salesforce Support team at least Ten working business days prior to the migration.
2. Provide <source realm code><site name> and <destination realm code><site name>
3. Specify the migration date in yyyy-MM-dd format in ticket.
4. Specify the time of migration in ticket in Customer's local timezone and specify time difference between customer timezone and US EST.

On the day of migration, the Support ticket must be updated with the information below as soon as site statuses have been changed:

1. The time when the old site is set to Maintenance mode. The migration process can be started only 90 mins after the old site is finally set to Maintenance mode. Make sure that, once the site status for the old site is changed to maintenance mode and migration process starts, the site is not changed to Online mode again, or else there will be data corruption.
2. The time when the new site is put to online mode. The new site should be marked Online at least 6 hours before the close of business customer's timezone, on the same day the old site is set to Maintenance mode.

1. Submit a Support case requesting to "Override new realm site with previously deployed Einstein site"
   • In the request, provide the following:
     • The new Production instance URL and Business Manager site
     • The old Production instance URL and Business Manager site
     • Confirmation that the data should be transitioned to the new instance
   • If you are a Partner submitting the request on behalf of a customer, the owner of the previous realm must also provide approval in the comments of the support ticket
2. When the new site goes live, Schedule Predictive Intelligence catalog and order jobs to run daily from new realm per site as outlined in How to Setup Predictive Intelligence Data (Einstein) Feed Process. 
3. Immediately after the new realm/sites feeds have been scheduled disable the old realm/sites feeds.
4. Support will override for customer prd/stg/dev unless there a specific reason for not to have it the same. 

• With the new Proxy Zone feature, you can simply create the zones on the new realm right away. If they already exists on the old realm, you will just see a yellow pop-up warning indicating that the Zone already exists.
• However, you can just click on "Create Zone" to continue. The zone will be created as a Proxy Zone on the new realm getting a dedicated CNAME.
• Once created and if you are ready to take traffic, you can activate the zone (Secure Zone), upload a valid SSL certificate, validate the TXT record and change the new CNAME from BM in DNS. More information can be seen in the "Create a Zone" information center topic.
• If you want to get rid of the zones in the old realm, this can be requested in a dedicated Support ticket.

17. Coupon Seed Migration (System-Generated codes only)

• When using system-generated coupon codes, migrating the coupon ‘seeds’ is essential for ensuring system-generated coupon codes remain valid in the new realm.
• If seeds are not migrated, previously issued coupons will cease to work due to dependency on these seeds for verification.
• This step is crucial for sites with active promotions using system-generated codes. To initiate this process, please open a support case with Salesforce Commerce Cloud Support with the subject “[Realm Move] Migrate Coupon Seeds”, specifying a list of the specific coupons you need to migrate.
• If you do not utilise system-generated coupon codes, this section does not apply.

Q&A
1) What elements don’t transfer?

• Payment instruments associated with orders cannot be transferred.
• Analytics data: Fresh Analytics data for the new realm will be available in Reports and Dashboards as well as Business Manager.
• ​​​Salesforce Payments Configuration: You will need to re-configure Salesforce Payments on the new realm.  
  • Note: To use Salesforce Payments on the new realm, Commerce Support team must enable the Salesforce Payments feature switch in Business Manager.

• Support will need to be engaged for importing orders as well as to reset on order and turn over values.
• Support can also assist with the movement of customer payment instruments if the process in How to export customer credit card data from Business Manager in B2C Commerce is not sufficient for your purposes.
• For any other data, the standard procedures for importing data that you want to migrate should be used.

• It depends on the reason why the split was decided.
• We encourage you to delete as soon as possible since both the old realm and the new realm will be live (as opposed to a POD move).

• Yes

• This depends on whether all the actions need to be performed at once and on the amount of data to be transferred during the cut-over window.
• You should migrate all the static data and as much dynamic data (customers, orders, etc.) as close as possible prior to the actual cut-over. Ideally, only the delta from the previous day should be required to copy during the cut-over to minimize the down time.

• This depends on how the Async payment functionality is implemented.

• The standard realm order form is required, since a new realm is provided to the customer.
• Standard data migration order form is required in case data is moved from a region to another.

• Open a case with Support and provide the forms requested in (7).

• It is highly recommended that the TDA for the account or a Solutions Partner be engaged for the whole duration of the project.