# Imports ### Overview Imports let you upload data into UbiQuity using a CSV or text file. This is the most straightforward way to get data into the platform when you are working with an exported list and do not need an ongoing automated connection. Imports are best suited for one-off uploads, occasional updates, campaign-specific lists, and bulk corrections. If you need data to flow into UbiQuity automatically on an ongoing basis, consider using a Connector or the API instead. All imports follow the same core process regardless of what you are importing: upload your file, map your columns to UbiQuity fields, configure how records should be created or updated, and run the import. *** ### What you can import UbiQuity supports two types of imports: **Contacts** — Add or update people in your database, including any profile or contact information you hold against them. See Importing Contacts. **Transactions** — Upload transactional or behavioural data linked to your contacts, such as purchase history or service records. See Importing Transactions. *** ### Things to keep in mind * Imports are manual. You need to run them each time you want to upload data. * Changes in your source data will not automatically update in UbiQuity. * Only CSV and text files are supported. Excel workbooks (.xls/.xlsx) are not accepted — save your file as a CSV before importing. * Clean, consistent data will reduce errors and improve results. UbiQuity validates data against field types during the import, so mismatched data will be rejected. *** ### Where to go next Choose the type of data you want to import: * [Importing contacts](#importing-contacts) * [Importing transactions](#importing-transactions) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ubiquity.co.nz/documentation/data-and-integrations/imports.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.