Public

Customer Data Center Migration Overview

Central Operations
Customer Migrations
Topics

 Overview
 Factors influencing the dates for Migration
 Migration Phases
 Planning & Execution
 Migration Execution details – BizX, LMS, WFA, ONB & JAM
 Pre-Migration Tasks / Considerations
 Post Migration Tasks
 Key points to remember

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 2

Customer Migrations
Overview

Introduction

 Customer Data Center Migration refers to moving customers’ existing HCM tenants to another HCM Data
Center

 Migrations environment (production vs preview) will remain the same, with few exceptions

 Migrations are initiated by CEE, Account Executives, or Services Sales team

 Service Engagement team works with the customer & operations to complete the initial scoping of this activity

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 3

Customer Migrations
Overview Contd..

The following items are required to be completed before migration can be scheduled

 Sales Team to create a quote in the CRM using the product SKU, SF-Data Center Migration (material code 8000988) for
9,398 USD. This is a flat fee for migrating all the customer’s instances & modules, except RMK*.

 Migration team cannot move forward with any planning activity until an approved & accepted sales order is reflected in the
Cloud Reporting system.
Note: Order number usually starts with “240” & is reflected under “Orders” section in Cloud Reporting

 A completed DC Migration Request Form with details of the instances & their product integrations .The migration team will
create the necessary JIRA tickets for tracking the migration, based on this request form.

 A service engagement order(SDC) need to be booked to complete initial scoping, by creating “Resource Request” directly
via Offline PDF form.

*RMK(Recruiting Marketing) migration tasks & cost needs to be scoped separately & tracked as a separate project.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 4

Customer Migrations
Factors influencing the dates for Migration

There are several factors influencing the final date for Migration other then the consensus from the customer.

Few are listed below:

 Completed sales order for Data Migration in Cloud Reporting

 Availability of a slot to migrate the customer (No conflicts with other migrations)

 Verification of any known conflicts with any maintenance activity or patch release, during that time

 CR approval by Change Advisory Board

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 5

Customer Migrations
Migration Phases

Post
Planning Execution
Migration

Complete Migration Cycle: apprx 4 weeks

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 6

Customer Migrations
Planning & Execution
CEE/CSM SDC Migrations Team

Provide completed DC Migration Check for the required details & create
Ensure Sales order is approved & reflected
Request form to Migration team per PROJOPS tickets
in CLD
customer/partner confirmation

Identify DB size, downtime & target space

*If partner is engaged for post migration effort* availability

Internal call with the Technical teams to

plan/schedule the Migration
Inform Customer on the Migration Schedule & Downtime

Provide the downtime details & migration

deck to the SDC/CSM/CEE/PM

Execution
Monitor the progress of the Migration & send
SDC/Partner to test new instance after performing the post migration activities notifications to the SDC/CSM/CEE/PM on
the progress

Inform customer on the completions of migration & post migration configurations/testing Inform SDC/CSM/CEE on the completion of
Migration

SDC & Partner are interchangeable for post migration tasks

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 7

Customer Migrations
Migration Execution - BizX

 Migration execution involves downtime for the customer when the system will not available for end users

 Duration of downtime depends on database size of customer system ( 100 GB may require 10 to 15 hours

& ~300 GB may require 15 to 18 hours of downtime)

 Source instance will be deactivated during the migration until it is purged.

 Target instance will mirror the source instance, as all data is moved across during this activity

 SFTP data is transferred to new SFTP account in the Target Datacenter.

 Scheduled jobs will be enabled

 Provisioning settings & static content including logos will be copied

 App team will confirm the completion of Migration, post the sanity checks.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 8

Customer Migrations
Migration Execution – LMS & iContent

 Migration execution involves downtime for the customer

 Maintenance page would be enabled on Source instance.

 New DB schema will be created & data would be copied from Source database pool to Target database pool

 iContent migration to be performed during production LMS migration as iContent is a shared resource

 SFTP account for the Source iContent would be stopped at least 3-4 days before the prod LMS migration to

allow for export of source data to target iContent server

 Target SFTP account for iContent would be provided by the Operations Team on the day of migration.

 iContent configurations update would be done by the Ops team after the LMS prod migration is completed.

 Migration team will confirm the completion of all activities, after validation by Operations team.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 9

Customer Migrations
Migration Execution – WFA, ONB & JAM

 Migration execution involves downtime for the customer.

 Migration for these modules can only be started post BizX migration completion.

 System will not be accessible by the Customer during the downtime.

 Data is copied from Source database pool to Target database pool .

 ETA for the migration completion would be 24 hrs after the BizX is migrated.

 JAM migration will be completed Monday following the BizX migration.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 10

Customer Migrations
Migration Execution – Boomi

 If the customer has Boomi integrations, Operations will provide Boomi access on the Target DC post BizX

migration.

 Partner/Customer admin will need to perform the following steps to integrate Boomi on the target instance:

 Create New atoms in Target DC clouds.

 Detach the Source DC Boomi atoms from the existing environments.

 Attach newly created Target DC atoms to the same environments.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 11

Customer Migrations
Pre-Migration Tasks / Considerations

 URL changes post Migration as below :

Module URL change?

BizX Yes
LMS No
WFA Yes
ONB Yes
JAM Yes

 New URLs for the Target Datacenter will be communicated by the Operations before the migration.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 12

Customer Migrations
Pre-Migration Tasks / Considerations Contd..

 Some of the Customer actions to be completed:

 Provide Manage Support Access
 Customers must replace all email addresses with dummy value or disable email notifications
(Foundation & LMS)
 Create test scripts, have access to all instances to be migrated & provide test users
 Customers need to whitelist the new URLs/IPs: (To be supplied by the Operations team)
 Main application URL, SFTP URL & Outbound mail servers
 Customer will receive credentials for the newly created target SFTP account 3-4 days before Migration
& will be responsible to forward them to the SDC consultant.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 13

Customer Migrations
Pre-Migration Tasks / Considerations Contd..

 SDC team to complete following:

 Provide general guidance to Customer - pre-migration tasks, migration request form, module related help etc..
 Pre-configuration work in BizX, LMS, WFA, ONB, JAM, RMK, RCM etc.
 Single Sign On
 Provide guidance as customer will need to disable
 Copy Settings & update as needed
 Review redirect URLs & static content
 Request Test users, Manage Support Access, SFTP accounts
 IP access restriction
 Advanced Reporting (ODS)
 Request provisioning access to the newly created target instance at least 4-5 days before migration(standard
SLA).
 Provide source & target SFTP account details to the Operations Team to transfer the SFTP data.

** PLEASE NOTE : HCP setup/migration needs to be performed as a separate project through a BCP ticket.**
© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 14
Customer Migrations
Post-Migration Tasks

 Migration team will notify SDC consultant regarding the completion of Migration.
 SDC to complete following:
 Notify customer that the Migration is complete
 SSO SAML applicable only.*
 This includes pre-migration disabling & post migration configuration (Login, Logout, redirect urls etc.)
 If required, customer will create a new dedicated case to troubleshoot any SSO issues encountered
post migration

 SFTP Job Setup

 SDC consultant will setup/update new SFTP account details in the scheduling jobs on the target instance.

 SDC will be responsible for all cross pillar integrations & configuration changes in BizX, LMS, WFA, ONB, JAM etc.

 SDC will be responsible for any sanity testing/validation of features like RCM, LMS, WFA etc.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 15

Customer Migrations
Post-Migration Tasks Contd..

 SDC will be responsible to raise Incident tickets with the replication steps & secondary logon credentials for any post
migration issues (https://jira.successfactors.com/servicedesk/customer/portal/1)

 Original instance in Source DC will be purged after two weeks from the migration completion post customer approval
only. It is kept disabled until then. Customer Service Manager/Project Manager/SDC to request approval to purge
instance & communicate to Operations.

*PLEASE NOTE: In case, SDC is not engaged, any post migration issue requires new individual dedicated cases to be
created (Customer Support Ticket in BCP). Please reference the original migration ticket (PROJOPS Ticket) on the CS
request.

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 16

Customer Migrations
Post-Migration Tasks Contd..

 Customer to complete following:

 Update new application Url’s in internal systems

 Deep linking of URLs, emails being pushed from SuccessFactors
 Outbound Mail Servers
 Re-enable email notifications/import email addresses/settings etc
 Customers using SSO for login must update the new URL in their internal system/portal
 Customers using Redirect URLs with Static Content must update with the new URL
 Custom integration work as applicable (a separate engagement may need to be scoped for this)
 Customers with job postings on external sites(LinkedIn, glass door etc.) must update the new url’s post migration
 Customer to communicate to its users about re-configuration of mobile app with the new instance
 Customer to verify & provide sign off that they have validated the instances have been migrated successfully
 Customer to communicate new url’s and system availability to their users

© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 17

Customer Migrations
Key points to remember
 Some special considerations when migrating to DC17:

 All stage(test) instances could only be migrated to preview environment except the EC (development) instance which resides on
production.

 RMK(Recruiting Marketing) migration needs to be analyzed for migration readiness for each customer.

 HCP in DC17 is expected to be available by Q3 2017 (this may change depending on CIS requirements)

 Disaster recovery in DC17 is actively being built on & is scheduled for completion in Q3 2017 to operate as a warm DR data center.
On this basis, if there is a disaster event after this completion date, then restoration would be at this new data center – Toronto2. In
the meantime, to fill the gap, Success Factors has committed to an “interim” DR solution to replicate some customer-specific data
from Toronto1 to a production environment in an SAP European data center (such as Amsterdam for ScotiaBank). This “interim” DR
solution is offered, as necessary, to Canadian sales prospects who desire the enhanced DR option (i.e., 24 hour RPO / 48 hour
RTO) for BizX / EC, LMS & Cloud Payroll.

 Audit is not available in DC17 preview & DC19 preview (ETA- to be checked)

 Some special considerations when migrating to DC2:

 RMK on DC2 is not available, RMK instance for the customers in DC2 will be setup on DC12.
© 2016 SAP SE or an SAP affiliate company. All rights reserved. Public 18
Thank you
HCM Service Delivery & Operations
Central Operations