Use One-Time Imports to upload a prepared CSV file and create or update records in InterAction+™ AI.
One-Time Imports help administrators bring structured data into InterAction+™ AI through a guided workflow. The import process supports sample templates, custom column layouts, reusable mapping instructions, matching rules, validation, status review, and error handling.
This helps firms manage project-based or ad hoc data loads without relying on separate legacy import tools.
In this article
- Why use One-Time Imports
- Who uses One-Time Imports
- Before you begin
- How One-Time Imports work
- Run a One-Time Import
- Review import results
- Tips for successful imports
Why use One-Time Imports
One-Time Imports provide a consistent way to create or update InterAction+™ AI records from a CSV file.
Use One-Time Imports when you need to:
- Add new records from a prepared file.
- Update existing records using mapped identifiers.
- Reuse mapping instructions for similar files.
- Validate source data before processing.
- Review warnings, skipped rows, failed rows, or records requiring review.
The workflow is designed to unify import capabilities into a single InterAction+™ AI import experience while preserving core capabilities such as mapping, rules, and validation.
Who uses One-Time Imports
| User | How they use One-Time Imports |
|---|---|
| CRM Administrator | Prepares and runs imports for project-based data loads. |
| Data Administrator | Creates or updates records, validates data, and reviews import results. |
| Data Stewards | Review warnings, skipped records, failed records, or records requiring review. |
| Reporting teams | Use imported data for reporting and downstream workflows. |
One-Time Imports are typically used for ad hoc or project-based data work.
Before you begin
Review the following requirements before running an import.
| Requirement | Details |
|---|---|
| Access | Authorized CIM access is required. |
| Permissions | The user must have Data Administrator group permission. |
| File format | The supported file format is CSV. |
| Encoding | The CSV file should use UTF-8 encoding. |
| Source data | Source values should be clean and prepared before upload. |
| Required identifiers | Required identifiers must be included for the selected import type. |
| Update imports | For updates, use record GUIDs or configured additional-field matching. |
| Review owner | Identify an owner to review warnings and rejected records. |
For update imports, Data Exports can be used to obtain contact or company GUIDs.
How One-Time Imports work
At a high level, a One-Time Import follows this process:
- Choose the data type and destination.
- Upload the CSV file.
- Reuse or create mapping instructions.
- Map required fields.
- Review matching and no-match rules.
- Validate the import.
- Review the status file.
- Correct errors, if needed.
- Run the import.
- Review the completed import results.
Run a One-Time Import
-
From the Home screen, select Data Management in the left navigation.
-
Open Data Imports.
- Select New Import.
- Select the data type you want to import.
-
Select where the imported records should be saved:
- My Contacts
- A folder
- A list
-
Download the sample template, or use a prepared CSV file with a custom column layout.
- Add your data to the CSV file.
- Drag and drop the file, or select Browse to upload it.
-
Map each source column to the corresponding InterAction field.
-
For updates, select the identifier InterAction should use to find existing contacts.
-
Choose what happens when no match is found.
- Configure any address or data-management options.
-
Save the mapping as a template if you want to reuse it for future files.
- Select Import to start processing.
Review import results
After the import is complete, open the completed import to review the results.
Review the import for:
- Skipped records
- Failed records
- Records in review
- Warnings
- Rejected rows
- Record counts
- Status details
- Error logs
Resolve exceptions as needed before considering the import complete.
Tips for successful imports
To reduce errors and make imports easier to review:
- Start with a representative sample, then scale.
- Use the sample template when possible.
- Confirm that required fields are mapped.
- Confirm that update imports include the correct identifiers.
- Reconcile counts, warnings, and rejected rows after every run.
- Assign a named owner to review import results and exceptions.