Print this page

Data.com: Restore Salesforce data after a Data.com Overwrite Clean job has run (for Administrators)

Knowledge Article Number 000198687
Description
You ran a Data.com Clean job and are unsatisfied with the resulting data. Now, you want to restore the Salesforce data to what it was before the job ran.
Resolution
Get files containing backup data for the Clean job from salesforce Customer Support and import the files into Salesforce using the Apex Data Loader by following a few steps.
  1. Grant login access to salesforce Customer Support, if you haven’t done so already.
  2. Contact salesforce Customer Support.
  3. Tell the support agent which Clean job(s) you’re unhappy with. You can review a list of completed Clean jobs from Setup by clicking Data.com Administration | Clean | Jobs. The Data.com support agent generates backup files for the selected Clean job(s), which are then available on the Documents tab.
  4. Visit the Documents tab to download all backup files for a job. (There may be multiple backup files for a job.) Files with “unchanged” in the name include records that have not been changed since the Clean job was run. Files with “changed” in the name include records that have been changed since the Clean job was run.
  5. Use the Apex Data Loader to import backup files into Salesforce. Make sure to select Use Bulk API in the Apex Data Loader Settings. You may have to manually map column headings in each backup file to fields in Salesforce. The automatic mapping setting only maps columns and fields that have the same name. Be careful if you’ve changed field names or mappings since the Clean job was run.
 
Considerations:
  • You can only restore data for completed jobs.
  • You can only restore data for jobs that have run within the past 21 days.
  • You can’t restore data for D&B company jobs.
  • You can’t restore data for manually cleaned records.
  • We suggest using the Apex Data Loader to import Clean job backup files into Salesforce. We do not support the Data Import Wizard for importing backup files.
  • Select Use Bulk API in the Apex Data Loader Settings.
  • When using the Apex Data Loader, you may need to map fields. The automatic mapping setting only maps columns and fields that have the same name. The administrator may have to manually map column headings in a backup file to fields in Salesforce.
  • The Apex Data Loader ignores blank values in the imported files. A value of #N/A in an imported file is loaded as null in Salesforce. This is the default behavior of the Bulk API mode, which is necessary to use when importing backup files.
  • The Apex Data Loader does not accept files with more than 50,000 rows. As a result of how Data.com Clean works, you may have multiple backup files with fewer than 50,000 rows.
  • Backup files will only include records that were changed by the Clean job that the customer is unhappy with.
  • The name of backup files takes the following format: <Object>_<Last 4 digits of job ID>_<Changed or Unchanged>_<Batch count>_<Timestamp in ms>.csv (e.g., Lead_1234_Changed_001_1399574083.csv).
  • We suggest you import backup files into Salesforce as soon as they are generated by a support agent. Backup data is divided into “unchanged” files and “changed” files. Data for records that have not been changed since the Clean job was run is in an “unchanged” file. Data for records that have been changed since the Clean job was run is in a “changed” file. This division may not be correct if an organization’s Salesforce data is changed after the backup files have been generated.




promote demote