SAP Knowledge Base Article - Public

2276692 - Best Practices on Migration option from JDM to JPB


  • Job Profile Builder is a replacement for legacy JDM.  At its core, it is a replacement for Families & Roles, but expands much beyond to allow customers to build complete Job Profiles with multiple content types.
  • Skills Management allows customers to capture employees’ skills within an Employee Profile portlet. 
  • Either of the above can be leveraged independently, but best practice would be to implement both.  This would truly help to solve the supply-and-demand issue by understanding both the organization’s roles as well as its employees. 
  • Customer (ONLY Existing customer) can use the migration button to migrate Families, Roles, Job Code to Role Mappings and Competencies to the new framework - Can only be done once all Job Profile builder configuration is completed
  • NEW Customer should configure all data directly via Job profile Builder options.


All HCM SuccessFactors Version/ Job Profile Builder

Reproducing the Issue

The migration job can be run via the backend to sync all existing data to Job profile builder.


  • Please note that once Job Profile Builder is enabled, do not manage Families and Roles from the Backend. The migration of Families and Roles only happens once and is not an ongoing sync.
  • It is not recommended to create data in JPB before running the migration job as it could have an impact on the Talent modules (Competencies / Behaviours ...).
  • Any update made via Backend (JDM) to Family names. adding Families, moving Roles from one family to another will not sync with Job Profile Data and will create sync issues.
  • The Sync job is recommended for existing customers during JPB implementation and should not be used to sync data created in provisioning after Job Profile Builder is already in use. A workaround for that is to create the exact same record in JPB UI as it should sync with the one in provisioning, but the best approach is that once JPB is enabled data should never be created or edited via provisioning.
  • JDM supports one to many mapping (same job code can be mapped to different roles) whereas JPB only supports one to one, during the migration job if system finds some incorrect mapping it will be skipped (our team is currently working on a fix for this issue).
  • Use JDM Check Tools to see if data is ready to migrate before a partner/support can proceed with the migration.
  • Use JPB Check Tools to search for any sync issues between JDM and JPB, as it should give you a list of data that exists in Provisioning/JDM but not in JPB, making it easier to fix.
  • Refer to the Help Portal Page on JPB enablement which covers data migration as well as how to use the check tools to your advantage in that process.


JPB Migration, JDM to JPB, Job Description Manager, Job Profile Builder , KBA , LOD-SF-CJ-JPB , Job Profile Builder , How To


SAP SuccessFactors HXM Suite all versions