Import and Export Data in SAP SuccessFactors Employee Central: Full Purge vs Incremental Load

Learn which import tool to use in Employee Central, how Full Purge and Incremental Load differ, and a safe routine that protects your data during mass loads and corrections.

Why Import and Export Data Matters

Every Employee Central project loads data in bulk. The organisation structure is loaded at the start, employee master data is migrated before go-live, and corrections arrive again and again during support. Doing this record by record in the screen is slow and easy to get wrong.

SAP provides import tools that read a CSV file and create or change many records at once. They are powerful, and that is exactly why they are risky. Choosing the wrong tool or the wrong purge type can overwrite or delete data you wanted to keep. This article explains the tools, the two purge types and a safe routine you can follow on every project.

The Import Tools You Will Meet

In Admin Center you search for the tool by name. Three tools matter for Employee Central:

ToolUsed forGood to know
Import Employee Data Employee-level data in Employee Central, such as personal information, address and job information. You download a template for each data type. Effective dates must be correct. It has a Full Purge option.
Import and Export Data Objects based on the Metadata Framework (MDF): generic objects, MDF-based foundation objects and your own custom objects. Also lets you download existing records, which makes it useful for backups and mass corrections.
Import Foundation Data The older, XML-based import for foundation objects. SAP has been moving foundation entities to Import and Export Data (see the note below).
Check which tool your entity needs

SAP's knowledge base article 2080139 explains that, since the 1H 2022 release, Import and Export Data should be used for several entities, including Job Classification Local, Job Family, Job Function, Pay Group, Cost Center, Pay Calendar and Geo Zone. The matching background jobs are the "MDF Data Import" and "MDF Data Export" jobs instead of "Foundation Data Import". Tool names and availability can change between releases, so check the current SAP guidance for your tenant.

Full Purge vs Incremental Load

Both purge types import the file you give them. The difference is what happens to the records that are already in the system but are not in your file.

Incremental LoadFull Purge
In one sentence Adds and updates the records in your file and leaves the rest alone. Replaces the existing records of the objects in your file with exactly what the file contains.
MDF objects History of an object with the same external code is not cleaned out. All records with the same external code as in the file are purged. Afterwards only the records from your file exist.
Typical use Day-to-day changes, new records, small corrections. First data migration, a complete reload, or removing wrong records on purpose.
Risk Lower. Wrong old records can stay behind unnoticed. High. Anything that is not in your file can be lost.
Before you run it Validate the file. Take a backup and make sure the file holds the complete history you want to keep.
Example: an import file with one corrected 2022 record. Incremental Load keeps the other records, Full Purge removes them.In the system now2020Analyst2022Senior Analyst2025ManagerYour import file2022Senior Analyst (corrected)After Incremental Load2020Analyst (kept)2022corrected (updated)2025Manager (kept)After Full Purge2020removed2022corrected2025removed
Figure 1: Same file, two purge types. Illustration with made-up job history.

Most objects in Employee Central are effective-dated, which means one object can have several time slices. If effective dating is new to you, read our article on Effective Dating in Employee Central first. It explains why a missing time slice in a Full Purge file simply disappears.

Rule of thumb

If you are not sure, choose Incremental Load and validate first. Use Full Purge only when you can explain exactly which records should exist afterwards.

Step by Step: Import and Export Data (MDF Objects)

  1. In Admin Center, search for Import and Export Data.
  2. Under the action to perform, choose Download Template and select the object, for example a generic object. The template always matches the current object definition.
  3. Open the CSV file and enter your data. Keep the header rows exactly as downloaded. For effective-dated objects, add one row per time slice.
  4. Save the file as CSV with UTF-8 encoding, so that special characters are kept.
  5. Go back to the page and choose the action Import Data. Select your file and the File Encoding (Unicode UTF-8 supports most languages).
  6. Choose the Purge Type: Incremental Load or Full Purge. Optionally you can suppress redundant date-effective records, which removes repeated entries and improves performance.
  7. Choose Validate first. Fix every error in the file, and only then choose Import.
  8. Check the job result. Failed steps appear in the job details, and the import result file lists the detailed error message for each row.
  9. Verify a few records in the system, for example with Manage Data, or export the object again and compare.

The same tool can export existing records. Exporting the objects you are about to change gives you an easy backup before every import.

Step by Step: Import Employee Data

  1. In Admin Center, search for Import Employee Data.
  2. Choose the data type, for example Address, and download its template.
  3. Fill in the template. Check the effective dates carefully: records of the same employee must not overlap, and the format of every date must match the template.
  4. If you are correcting existing data, first back up the current records, for example with an ad hoc report, and prepare the corrected rows from it. Copy and paste is faster when the report columns match the template.
  5. Upload the file. Tick the Full Purge option only when you want to replace the complete history of that data type for the employees in the file.
  6. Run the import, review the result and error messages, and check a few employees on their profile.
Loading order matters

Employee data builds on other data. Users and the person and employment records must exist before the data that depends on them, and organisation objects such as departments must exist before employees can reference them. Always follow the loading sequence in SAP's data migration guidance for your scenario.

A Safe Import Routine

  1. Back up first. Export the affected records or run an ad hoc report and keep the file.
  2. Download a fresh template. After any data model or object definition change, old templates are out of date.
  3. Test in a non-production system before you touch production.
  4. Start small. Import five records and check them before you load thousands.
  5. Validate before you import. Fix errors in the file, not in the system.
  6. Choose the purge type deliberately and say it out loud: "after this import, which records exist?"
  7. Read the result file even when the job shows success.
  8. Verify and document. Check records in the screen and keep the file, date and purpose of every import.

Common Errors and What to Do

ProblemUsual causeWhat to do
Columns do not match the systemThe data model or object definition changed after you downloaded the template.Download a fresh template and copy your data into it.
Reference or code not foundThe parent object, picklist value or external code does not exist, or is spelled differently.Load the parent objects first and compare the external codes character by character.
Date errorsWrong date format, overlapping effective dates, or an end date before a start date.Use the format from the template and check that time slices of one record follow each other.
Mandatory field missingThe configuration requires a field that the file leaves empty.Fill every required column. Check the configuration if the requirement is unexpected.
Special characters look wrongThe file was not saved as UTF-8.Save as CSV UTF-8 and select the same encoding during the import.
You are not allowed to importYour permission role does not include the tool or the object.Ask your administrator to check the role-based permissions.
Records disappeared after the importFull Purge was used and the file did not contain every record.Restore from your backup file with a new import, and review the purge type for next time.

Typical Project Scenarios

These are common patterns on projects, not statements about specific companies.

  • First load of the organisation structure. Locations, legal entities, business units and departments are loaded as MDF objects, parents before children, usually with Full Purge on an empty system.
  • Mass correction of descriptions. Export the objects, correct the text in the CSV, and import with Incremental Load so that history stays untouched.
  • Cleaning up wrong address history. Back up the employee's records, prepare the complete corrected set of rows, and run a Full Purge for that data type only for the affected employees.
  • New cost centres from finance. Finance sends a list. You add the rows to a fresh template and load them incrementally.

Interview Questions

1. What is the difference between Full Purge and Incremental Load?

Incremental Load adds and updates the records in the file and leaves other existing records alone. Full Purge replaces the existing records of the objects in the file with exactly the records from the file, so anything not in the file is removed.

2. Which tool imports MDF-based objects?

Import and Export Data in Admin Center. You download a template, fill it, validate it and import it. The same tool can also export existing records.

3. What do you do before running a Full Purge?

Take a backup of the current records, make sure the file contains the complete history you want to keep, test in a non-production system and validate the file.

4. Why must parent objects be loaded before child objects?

Child records reference their parents, for example a department references a business unit. If the parent does not exist, the reference cannot be resolved and the row fails.

5. Where do you see the reason for a failed row?

In the job details of the import, and in the import result file, which lists the error message for each failed row.

6. Why do you download a fresh template for every import?

The template is generated from the current object definition or data model. After a configuration change, an old template can have missing or extra columns.

Frequently Asked Questions

Is Incremental Load always safe?

It is safer than Full Purge, but not risk-free. A wrong value in the file will still overwrite the correct value, and wrong old records may stay behind. Always validate and verify.

Can I use the import tools to delete data?

Full Purge can remove records that are not in the file, and some objects support removal in other ways. Treat every deletion as permanent and take a backup first.

Do I need an administrator role to use these tools?

You need the right permissions in your role-based permission setup for the tool and for the objects you load. If a tool is missing, ask your administrator.

Conclusion

The import tools save hours, and the purge type decides whether they also save your data. Remember the three habits: back up before you change, validate before you import, and choose Full Purge only when you can say exactly which records should exist afterwards. With those habits, mass loading becomes one of the safest and most useful skills in your Employee Central toolbox.

SAPwithSAI

Practical SAP SuccessFactors Employee Central and SAP CPI learning for consultants.