Export: Add / Update



  • Export data from a Data Source to a Data Target with user-specified mapping between attributes from the input Data Source to the attributes in the output Data Target.
  • Use this task to write data to a Data Target such as Salesforce, Marketo, etc. at the end of a Job.


Field Description

  • Records that were updated after – will only export records updated after the date specified.
  • Export all filtered records regardless of whether it was updated in the job – if this box is checked, all the records in the job will be exported. In order to export only modified records, leave the box unchecked.
    Background: Openprise has built-in intelligence to reduce redundant work when exporting data. When this box is unchecked, Openprise checks each record selected by the task’s filter to see if the target data attributes have been modified, and only exports those records, and attributes within the records, that have been changed. For example, if the email field has been cleaned, and the clean result is the same as the original value, Openprise will omit updating the email field when exporting. Typically, this box can remain unchecked for efficiency in processing. If you find that the job running this task does not update your data target as expected, try checking the box and re-running the job.  
  • Select Data Target – Select a Data Target to export data.
  • To
  • – fields in the Data Target
  • From – fields from job to upload

Note: if an attribute containing an ID of the target system is supplied on the Export task, Openprise assumes the action should be an update to the target system. If there is no attribute supplied for ID, Openprise assumes the action should be the creation of a new record in the target system. Therefore, you cannot mix inserts and updates in the same task.


  • If you supply an attribute for ID, Openprise assumes you are updating the record associated with the The Data Target must already exist.
  • If the Data Target has required attributes, they are marked in red and must have mappings defined.
  • In order to map an attribute from the Data Target, the attribute must be part of the Data Target configuration.
  • It is possible to have multiple tasks output to the same Data Target, so be careful to avoid unintended collisions.
  • The output data set will contain the following attribute fields which can be used for additional processing:
    • op_export_errors – This is a text field that contains error messages that occurred (if any).
    • op_export_reference – This contains a reference to the element in the target data set operated on by the task. For instance, if you are adding leads to Salesforce, this will contain the lead ID of the lead added. When adding leads to Marketo, it does NOT contain the Marketo ID of the created records, but instead contains an id associated with processing the update.
    • op_export_status – This contains the action performed: insert, update or delete.
    • op_export_success – Boolean field that contains yes/no depending on the success of the operation.
    • op_export_time – Time stamp of the action taken by the task.
  • For creating a CSV file in Google drive, Box or Dropbox, use the Upload File task.



  1. Push cleaned and normalized data back into SFDC, Marketo, Eloqua, Pardot, etc.
  2. Push enriched and cleaned data into a data warehouse (Redshift, RDS).


Support Contacts

If you have any additional questions, please feel free to contact us at support@openprisetech.com.


Leave a comment