---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Run or schedule a data import

# Run or schedule a data import {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Specify when to run a data import by creating a schedule. Schedule an import to run
at a specific time, at regular intervals, or after a parent import. You can also run your
import immediately.

## Before you begin

[Configure a data source](https://www.servicenow.com/docs/vABw~5GBidDzvkTLLV6HbA "Start importing data with Integration Hub by creating a data source. A data source specifies how and where to get the data you want to import."), then [Map source data to a target table](https://www.servicenow.com/docs/wd8QH1JWzIxgASGMDX2esg "Specify how source data is transformed to your target tables.").

Role required: admin or ih_import.

## Procedure

1. Navigate to AllIntegrationHubIntegrationHub - Import.
2. On the landing page, select your integration.
3. On the left navigation panel, click Schedule imports.
4. On the Run and schedule imports page, click Schedule an import.
5. On the New schedule form, fill in the fields.  
   {#run-schedule-data-imports__table_sjb_jk2_lpb__entry__2}

   | Field | Description |
   |-|-|
   | Scheduled Data Import ||
   | Name | Name to uniquely identify the import schedule. |
   | Data source | Data source for the import. This field is automatically set to the name of your integration. |
   | Run as | Name of the user or user role the import executes with. For example, the import may run as the System Administrator, or it may run with the roles of a specified user. |
   | Application | Application scope for the import schedule. |
   | Run | Option to specify when the import runs. Select one of the following. * Daily: Runs every day. * Weekly: Runs every week. * Monthly: Runs every month. * Periodically: Runs at regular intervals. * After Parent Runs: Runs after another import. {#run-schedule-data-imports__ul_zfc_mgf_lpb} |
   | Day | Day of the week or month to run the import. Entered as a number. This field appears only when Weekly or Monthly is selected from Run. |
   | Repeat interval | Amount of time to wait between imports. Entered in days, hours, minutes, and seconds. This field appears only when Periodically is selected from Run. |
   | Parent | Name of the parent import. The parent import must finish before the current import begins. This field appears only when After Parent Runs is selected from Run. |
   | Time | Time of day to run the import. Entered in hours, minutes, and seconds. |
   | Active | Option to make the import schedule active. |
   | Advanced ||
   | Concurrent import | Option to divide the data into multiple import sets and process them concurrently. |
   | Partition Method | Option to specify how to partition the data. Select one of the following. * Custom size * Round Robin {#run-schedule-data-imports__ul_vhh_p3f_lpb}This field appears only when Concurrent import is selected. |
   | Partition Size | Number of records for the partition size. Must be greater than or equal to 1000. This field appears only when Custom size is selected from Partition Method. |
   [ ]

   {#run-schedule-data-imports__table_sjb_jk2_lpb}
6. Click Save.
7. **Optional:** To add a prescript or postscript, click the more options icon (![More options icon]()) and select Advanced setup.  
   This option opens the form for the scheduled data import, where you can add a script to run before or after your import.
8. **Optional:** Run your scheduled import right away by clicking the Run Import button, and refresh the Executions list to view the execution record.

## What to do next

Your import will run at the scheduled time. After it runs, an Executions section
appears on the Run and schedule imports page. The Execution section has execution
records where you can view details about your import, including its runtime, the
number of imported rows, and any errors or log messages.

*[\>]: and then