Different data loaders are available for Sage People, each suited to specific scenarios. Use this guide to select the correct tool and understand its capabilities.
Selecting your tool by scenario
| Scenario |
Recommended Tool |
|---|---|
| I want to do the main data load for my organization |
Sage People Data Loader |
| I want to load historical absence requests | Sage People Data Loader |
| I want to mass delete all data | Sage People Data Loader |
| I have lots of data to load or delete in a single object that the Sage People Data Loader doesn’t cover. For example, passports and visas |
Salesforce Apex DataLoader |
| I want to mass upload attachments |
Salesforce Apex DataLoader |
| I want to load historical absence requests with data in the Notes field. |
Salesforce Dataloader.io or Salesforce Apex DataLoader |
Benefits and limitations of each data loader
We've outlined the pros and cons of each method below. We haven't documented Salesforce Import Wizard, but you can find details on how to use it here. Salesforce help content for the Data Import Wizard.
| Sage People Data Loader | Salesforce Apex Data Loader | Salesforce Dataloader.io |
|---|---|---|
|
You can import data into the three main Sage People objects (Team Member, Employment and Salary) simultaneously. |
You can only load data into a single object at a time. | You can only load data into a single object at a time. |
| You can mass delete all Sage People data simultaneously. | You can only delete data in one object at a time. | You can only delete data in one object at a time. |
| Sage People verifies your data so any data errors prevent the system updating any records. This can be an advantage when you want to upload records sequentially for auto-numbering purposes. | Sage People verifies your data so errors in any row prevent that record from updating. The system still uploads all records without errors. This can be a disadvantage when you want to load records sequentially for auto-numbering purposes. But it can be quicker if auto-numbering isn't a concern. | Sage People verifies your data so errors in any row prevent that record from updating. The system still uploads all records without errors. This can be a disadvantage when you want to load records sequentially for auto-numbering purposes. |
| You can generate data load templates. | You can only generate a data load template by exporting a blank CSV file for the object. | You can only generate a data load template by exporting a blank CSV file for the object. |
| You can export picklist options for each picklist in an object simultaneously. | You can't export picklist values. | You can't export picklist values. |
| You need to edit a CSV file in a text editor to ensure the correct format. | Accepts All CSV files. | Accepts All CSV files. |
| Can only import into specific objects available for data loads. | Can import into all Salesforce objects. | Can import into all Salesforce objects. |
| Main Data loads can take a long time. Likely due to the verification and importing into multiple objects at once. | Generally, uploads are quicker than Sage People Data Loader. | Generally, uploads are quicker than Sage People Data Loader. |
| Can't delete from a single object or filter deletes. | Can delete from a single object and filter deletes. | Can delete from a single object and filter deletes. |
| Can't export so have to use Salesforce reports instead. | Can export. | Can export. |
| Can't export so you can't take backup before the load to roll back later. However, the system retains a copy of all successful and unsuccessful data loads in the Data Loads tab. | Can easily create a backup before importing and changing data, but doesn't store data. | Improved data security as can most easily create a backup before importing. stores that backup for 30 days. |
| Good UI. | Slower and UI not as good as Salesforce Dataloader.io. | Quicker, easier and superior UI to Salesforce Apex Data Loader. |
| you can load lookup values in without specifying the reference field. Validates against lookup values in the system. | When importing lookup fields, you must use Salesforce IDs. | When importing lookup fields, you can select the reference field so you don't always need Salesforce IDs. |
| No monthly limits. | No monthly limits. | Has a monthly limit of 10,000 records per month that you can import, export or delete per Admin User. You can create more admin users to extend this. |
| Keeps tasks indefinitely so you can go back to tasks you already completed and easily rerun. | No history log to refer back to past tasks. | Keeps tasks for 30 days so you can go back to tasks you already completed and easily rerun. |
| Native within Sage People so you don't need an additional login. | Prompts you to log in each time. | The auto login feature means if you're signed into multiple Salesforce orgs at a time, it won't pick up the wrong org. It's best to sign out of all orgs other than the one you wish to import into. |
| You can't import mass attachments with a source file. | Use for mass importing attachments. | You can't import mass attachments with a source file. |
| You can't use it for exporting. | Allows you to filter the records you're exporting. | Allows you to filter the records you're exporting. |
| You can't use it for exporting. | You can specify the date format in Settings only. | Allows you to specify the date format for each import easily. |
| Sage People supports this. | Sage People doesn't support this, but you can raise a Salesforce case. | Sage People doesn't support this. |
| Works on Macs. | Works on Macs. | Works on Macs. |
| Must run a report to see the data. | Must export to see data to correct. | Must export to see data to correct. |
| High volumes of data can cause the Sage People Data Loader to run slowly. | Works well with high volumes of data. | Works well with high volumes of data. |
| Unable to load data that contains line breaks. For example, sentences on separate lines in a long text field. This is due to the file format the data loader requires for upload. | Can load data containing line breaks. For example, sentences on separate lines in a long text field. | Can load data containing line breaks. For example, sentences on separate lines in a long text field. |