I wanted to share our successful implementation of custom onboarding data migration using the BTP Extensibility Wizard. We had a unique challenge: migrating 2,500 in-progress onboarding cases from a legacy system that used completely different field names and structures than SuccessFactors Onboarding 2.0. The standard import templates didn’t support our custom fields, and manual remapping would have taken weeks. Using the BTP Extensibility Wizard, we were able to create a custom mapping layer that automatically transformed our legacy data format into SuccessFactors-compatible structure. The wizard’s visual field mapping interface made it easy to map 45 custom fields, and the built-in validation rules caught data quality issues before import. The entire migration completed in 3 days instead of the estimated 3 weeks, with a 95% success rate on first import. The onboarding workflow updates triggered automatically after import, so new hires experienced no disruption. Happy to share technical details if anyone is considering a similar approach.
This is really interesting! I’ve used the BTP Extensibility Wizard for API extensions but never considered it for data migration scenarios. Can you elaborate on how you set up the mapping layer? Did you use the wizard to generate transformation logic, or did you write custom code? Also, what did you do for the 5% of records that failed on first import?
Our team had minimal BTP experience - just one developer who had completed the BTP fundamentals course. The wizard is designed to be low-code, so the learning curve was manageable. For ongoing maintenance, you can update mappings without full redeployment. The wizard saves your mapping configuration as a JSON file that you can version control. When we added 5 new custom fields last month, it took about 30 minutes to update the mapping and test. Much easier than reconfiguring a traditional ETL tool.
The BTP approach is definitely more sophisticated than standard CSV import, but I’m curious about the learning curve. How much BTP expertise did your team have going into this? And what about ongoing maintenance - if you need to add more custom fields to onboarding later, can you easily update the mapping configuration, or does it require redeploying the extension?