Skip to Content
Technical Articles
Author's profile photo Lalitha KR

Leverage Integration Center to migrate/create employee records

In this blog post, you can learn how Integration Center can be leveraged to migrate or create employee records in SuccessFactors system.

While working as Data Migration Lead, there came a requirement for the SF administrators to add small population of records into the system on monthly basis. EC is still not the master for these, hiring is done in other Source system and data would be sent in excel to add them to SF system.

In such scenario, administrators can use either “Add New Employee” option or “Import Employee Data” option.

Add New Employee is suitable when number of records to be added are less, it needs to be done one by one.

Import Employee Data is suitable for mass hiring, more suitable for initial data migration. One needs to prepare the import file for each portlet and run the import for each portlet in sequence. To add a record for all the portlets (assuming all portlets are in scope), nearly 17-18 import files to be prepared and run in sequence.

This triggered me to try out Integration Center to migrate/create records. Inbound Integration is built adding all portlets in scope, in the recommended employee import sequence. This can be scheduled to run on regular basis, based on Client need. The file containing details of all portlets (Single CSV file) to be placed in SFTP. Once scheduled job runs successfully, user record gets created.

Steps to build the Integration Center Job:-

Step 1. Admin Center -> Integration Center -> My Integrations -> Create -> Click on “Scheduled CSV Input Integration.”

Step 2. Select the starting entity. It can be any entity to start with. We can later add all other entities as needed.

Step 3. Name the Integration Center Job

Step 4. Go to Configure Fields tab -> Upload Sample CSV

Here, prepare the file including all portlets. Use single header. These portlets should be in the order of import sequence. Fields to be added next to each other for all portlets – as given in the sample csv file

Step 5. Once csv file is updated, the fields in the csv file are added to the integration as shown below

Step 6. Add the data entities in the recommended Import sequence – example as shown below.

Step 7. Map the source file fields (fields added from csv file) to relevant destination fields (portlets added here). This needs to be done for all the entities added here.

Step 8. Set the Source settings in terms of SFTP server details, file name & folder details. The CSV file to be placed in the sftp folder, the one mentioned in the server details.

Step 9. Schedule this job. Or run this job manually once file is placed in SFTP. Once scheduled job is completed successfully, user record gets created.

Some benefits are :-

  • User records can be created for multiple portlets using single Integration center job, no need to prepare multiple import templates / run multiple Import jobs (Import employee data in SF)
  • Integration job can be scheduled for the system to create records without any manual intervention of administrators.
  • Automation of the task
  • Integration job is reusable in other instances.

Reference KBA :

Thank You !

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Kandadi Sreelatha
      Kandadi Sreelatha

      Detailed and helpful blog: -)

      Author's profile photo Lalitha KR
      Lalitha KR
      Blog Post Author

      Thanks Sreelatha

      Author's profile photo Narendra Nathawat
      Narendra Nathawat

      Very helpful Lalitha. I wish you had written this blog couple of years earlier would have saved me a ton of time.

      Thanks for sharing knowledge. Much Appreciate.


      Narendra Nathawat

      Author's profile photo Lalitha KR
      Lalitha KR
      Blog Post Author

      Thanks Narendra

      Author's profile photo Dharnish Shivakumar
      Dharnish Shivakumar

      Thank You for the detailed explanation. This is super helpful!

      Author's profile photo Lalitha KR
      Lalitha KR
      Blog Post Author

      Thanks Dharnish

      Author's profile photo Amar ZERDAZI
      Amar ZERDAZI

      Interesting blog Lalitha. Thank you for sharing. Let's try to implement it then 😉

      Author's profile photo Lalitha KR
      Lalitha KR
      Blog Post Author

      Thanks Amar! yes, we should 🙂

      Author's profile photo Shilin Song
      Shilin Song

      Hi Lalitha,


      Great Blog!

      But I have some questions about it.

      First, if all entities are imported in a single integration job, how do you make sure the data is imported in order (user, personal info, employee detail, job info....)? As you know, the import sequency is important for SF to create a user record.

      Secondly, whether it supports importing a 1:M entity data in the file, such as business email and personal email?

      Looking forward to your reply.

      Thank Berg

      Author's profile photo Lalitha KR
      Lalitha KR
      Blog Post Author

      Hi Shilin,

      Thank you for referring to my blog 🙂 Regarding your questions,

      1. I have mentioned in Step 4 and Step 6 that, both csv file and adding entities to Integration to be in the SAP recommended import sequence. This is expected process to be followed for the system to work as expected. When integration runs, it actually runs in this sequence and for any portlet any issue comes up (Ex: biographical), it will stop processing the rest of the portlets which comes after this portlet, this means it executes in sequence.
      2. For such options, where in, for the same portlets, 2 data types to be added, I don't think it is possible in single csv template. I tried it for Pay component recurring, could not do it 🙂 Might be we should explore it further 🙂

      Many thanks