3628980 - KSA Migration: DC23 - DC82 - Customer Checklist

Phase

Activity

Description

Complete By

Pre-Migration

Notify end users about the service downtime and the updated URLs

Notify all end users in advance about the planned service downtime, including the exact date and time of the outage, expected duration, and the reason for the interruption. Additionally, clearly communicate the new URLs that will be used post-migration or update, along with any necessary instructions to ensure a smooth transition and continued access to the services

T-30 days

Pre-Migration

Customer to provide details of all non-SAP SFTP servers, including Source IP, Hostname and Port

 The customer is requested to share the complete details of all non-SAP SFTP servers—specifically the Source IP, Hostname, and Port—so that these can be allowlisted on the SAP side to ensure uninterrupted communication.

KBA-> 3122406 - How to connect SuccessFactors to a new third-party site (allowlist on SAP side)

T-30 days

Pre-Migration

Document all integrations and use cases necessary for validating the target instance after migration

Customer to document all relevant integrations and associated use cases that will be essential to validate the functionality, performance, and data integrity of the target instance following the migration. This should include both inbound and outbound interfaces, third-party system connections, scheduled jobs, and any critical business scenarios that must be tested to ensure a successful transition

T-15 days

Pre-Migration

Allowlist the new outbound IPs for DC82, including 3rd party servers

Ensure that the new outbound IP addresses associated with DC82 are added to the allowlist on all relevant systems, including firewalls, integration endpoints and any third-party services that require IP-based access controls. This step is critical to maintaining uninterrupted connectivity and ensuring smooth communication between DC82 and external systems post-migration

KBA -> 2089448 - SuccessFactors Data Center Name, Location, URL, Domain Name, Mail Server details, SFTP details and Outbound IP addresses - SAP for Me

T-15 days

Pre-Migration

Allowlist the DC82 Email servers

Ensure the email servers associated with DC82 are added to the allowlist on all relevant systems, including mail gateways, spam filters, and any third-party email security solutions. This is essential to prevent legitimate emails from DC82 from being blocked or marked as spam, and to maintain reliable email communication post-migration

KBA -> 2089448 - SuccessFactors Data Center Name, Location, URL, Domain Name, Mail Server details, SFTP details and Outbound IP addresses - SAP for Me

T-15 days

Pre-Migration

Customers will need to switch to DigiCert G5

SAP SuccessFactors will switch to DigiCert G5. If customers have systems in which they manage the trusted certificates themselves, they need check if the Digicert G5 Root certificate exists in it. If it exists and the usage is related to SAP SuccessFactors, then customers will need to add the G5 Root certificate to it

KBA-> 3626800 - SAP SuccessFactors HCM SSL Certificate DigiCert Global Root CA change to "DigiCert TLS RSA4096 Root G5" 

T-15 days

Pre-Migration

Notify all ONB internal users and hiring managers that emails will be triggered for in-flight candidates during the onboarding and offboarding process, including the new URL and pending task reminders; notifications scheduled for future dates, along with those from the past 90 days, will also be retriggered by default 

The ONB 1.0 email trigger is designed to ensure that all in-flight candidates (those currently in the onboarding or offboarding process) receive the updated onboarding URL when their Production environment is migrated to a new URL. Since these notifications are intended for all in-flight candidates, customers must ensure that only relevant/actual in-flight users exist in the system. Please refer to the KBAs below to follow post-account refresh best practices for masking or redirecting emails of non-actual/non-relevant in-flight candidates, so that notifications are delivered only to valid candidates

KBAs->

2630586 - The Account Refresh Process for Onboarding 1.0 - SAP for Me 

2546134 - How to Mass Update the Email of all Users - Onboarding 1.0 - SAP for Me 

T-14 days

Post-Migration

Set up all required integrations involving all SAP systems excluding SuccessFactors

Customers are required to re-configure all their non SuccessFactors, SAP configuration. Customer will need to de-register and re-register to the BTP platform

Help Guide-> Configuring Integration Between SAP SuccessFactors and SAP BTP

T-0 days

Post-Migration

Set up required integrations involving 3rd party external systems

1) Customer will need to establish authentication for 3rd party integration for API calls, for which customers will need to generate a Security Assertion Markup Language (SAML) assertion for requesting an OAuth token through the new URL

Help Guide-> Generating a SAML Assertion

2) Configure non-SAP Single Sign-on. Customers using 3rd party IDP provider needs to work with their vendor to update configurations customers would need to update the SAML metadata on corporate IDP and apps using generic IDP

Help Guide-> Guidelines When Using Third-Party Identity Provider 

3) If any FTP calls hard coded with IP addresses must be validated and adjusted with new Data center IP address if required.

4) Any external/custom integration with SAP Jam (involving OAuth Clients, SAML Trusted IdPs, Jam APIs) will require Jam URLs to be updated on the external end of the integration. Standard integrations (BizX, IAS, LMS) with Jam will be handled by SAP. 

KBA-> 3638405 - KSA Migration - DC23 to DC82 - SuccessFactors URLs

T-0 days

Post-Migration

Update SuccessFactors Keys in Mobile Device Management (MDM)

Admin will need to update the SuccessFactors key in their Mobile Device Management (MDM) system, if applicable.

KBA: 2285307 - Mobile Device Management support for SAP SF Mobile App [SF MOB]

T-0 days

Post-Migration

Re-activate mobile application

Update the SuccessFactors Mobile App from Apple App Store or Google Play Store and reactivate their mobile application post migration

KBA-> 2550363 - How to activate / authenticate / login on SuccessFactors App? [SF MOB]

T-0 days

Post-Migration

Setting up standard integrations on Dell Boomi

Part of standard SuccessFactors integrations

KBA-> 3631192 - SuccessFactors DC23 to DC82 Migration – Standard Integration Task

 . KBA - 3094102 - SuccessFactors - How to update the provisioning Assertion Consumer settings and change the signature algorithm?

T-0 days

Post-Migration

Setting up standard integrations on SAP Cloud Integration (CI)

T-0 days

Post-Migration

Configuring Integration Center and Business Scenarios

T-0 days

Post-Migration

Setting up Integration Gateway

T-0 days

Post-Migration

Resolving connectivity issues with External Subscription Management (EEN)

T-0 days

Post-Migration

Reconfigure any external applications using SuccessFactors as the Identity Provider.

Post migration any external/non-SF applications using SuccessFactors as IdP will need to re-establish the single sign-on setup with the updated SuccessFactors SSO metadata file.

KBA-> 2707993 - [SSO] Metadata file for SSO | How to generate it for either SF x IDP and Outbound SSO scenarios 
[Scenario 2: SSO between BizX SuccessFactors (as the Identity Provider) and a third-party system]

T-0 days

Post-Migration

Update SAP SuccessFactors SFTP URL

During the Preview cutover window -

• Update the SAP SuccessFactors SFTP to the new target URL during the Preview cutover window.
• The new SFTP host key will need to be accepted on the customer end for any third-party setup connecting to SFTP
  KBA-> 3665397 - SFTP Server RSA Key fingerprint - DC82 - SAP SuccessFactors

T-0 days

Post-Migration

Re-configuration of ECSC- Ask HR

Customers are required to reconfigure ECSC- Ask HR to update the new BizX URL.  This step is required for ECSC customers only.

KBA-> 3638836 - Reconfiguring your NEO ECSC instance after KSA Migration (KSA customers Only)

T-0 days

Post-Migration

Re-configuration of EC Payroll

Customers are required to re-configure EC Payroll to update the new BizX URL.  This step is required for EC Payroll customers only.

KBA-> 3628149 - ECP - BizX Data Center Migration

T-0 days

Post-Migration

Re-configuration of SuccessFactors Work Zone

Customers are required to re-configure SuccessFactors Work Zone to update the new BizX application & API URLs.  This step is required for SuccessFactors Work Zone customers only.

KBA-> 3636381 - KSA Migration: DC23 - DC82 - SAP SuccessFactors Work Zone updates

T-0 days

Post-Migration

Resend "Ask for feedback" email incoming mails to DC23 mail servers post cutover

"Ask for feedback" email request sent before this infrastructure change will not be working and can't be responded successfully by the email recipient after the infrastructure change.

KBA-> 3624006 - DC23 Migration - Resend Ask for Feedback emails

T-0 days

Post-Migration

Recruiters should reconnect with candidates to maintain communication flow

The Message Center feature within RCM is affected by this migration. Any conversations initiated between recruiters and candidates prior to the migration will not reflect replies from candidates if they respond to older email threads. Recruiters will not receive candidate replies sent via pre-migration email threads.

Recruiters can start a new conversation or replying to the previous message to generate an updated link for continued engagement.

KBA-> 3631217 - [Action Required for DC 82] Impact of DC 23 to DC 82 migration on Recruiting Emails - Recruiting Management

Note: RMK Career URL will change from DC23 Preview to DC82 Preview. Post cutover to new DC, customers and candidates would need to start using the new Career URLs :

• Pre-migration DC23 URL - <customer>.valhalla23.stage.jobs2web.com
• Post-migration DC82 URL - <customer>.valhalla82.stage.jobs2web.com 
• IP Address - rmk82.jobs2web.com - 34.166.153.97 

No change in Career URL for DC23 Production to DC82 Production.

T-0 days

Post-Migration

Customers using 'A' record to update RMK DNS entry

Customers using A records, instead of CNAME pointing to the jobs2web.com address provided earlier, must update their RMK DNS entry within 10 days following the cutover. While traffic will be temporarily redirected for 10 days post-migration, customers are strongly advised to schedule and complete this DNS change as soon as possible to ensure uninterrupted service.

• IP Address for DC82 - 34.166.153.97 

T-0 days

Post-Migration

Customers need to re-configure their ICS (Internal Career Site) configuration

In Preview, For the Internal Career Site (powered by CSB), the site URL will change after migration. This must be updated in the IAS console under the CSB application by the IAS administrator.

Additionally, the administrator will need to regenerate the metadata in CSB > Settings > IDP configuration and reupload it to IAS.

Failure to update the URL will result in ICS not working after the migration.

Related KBA with steps: 3433394 - Changes and required actions related to Planned Preview migration - Recruiting Marketing

T-0 days

Post-Migration

Functional testing

It is essential for customers to perform functional testing to ensure their business processes and integrations continue to work as expected in the new environment.

T-0 days

Post-Migration

Resend emails with deep-links pointing to the new DC82

Following the migration, customers in DC82 will be assigned a new domain. Emails sent prior to the migration that contain deep links using the old domain will stop functioning 30 days following the migration date. Customers are advised to either respond to these emails within the 30-days window or resend them using updated links with the new domain.

T-0 days