Summary
CSV and other file-based imports are likely the fastest and lowest-friction way to get initial contact data into TruAgents. They are especially useful when a team wants to launch quickly before setting up a deeper ongoing sync.Who this is for
Technical admins and operators connecting external systems to TruAgents.Where it fits in the product
- Contacts → Data Sources
- onboarding and first-import flows
Why file imports matter
The app already suggests a file-upload path with column mapping, which usually makes file imports the most practical first-run option for teams that are still organizing their source systems. The current implementation also hints that this path supports more than just strict.csv files. Spreadsheet-style uploads can still be part of the same import-and-map workflow.
Typical file-import flow
- choose the file-upload import path
- upload the source file
- inspect detected columns
- map those columns into TruAgents contact fields
- import the contacts
- review the resulting records before using them in segments or campaigns
Why mapping matters here
File imports are fast, but they put more responsibility on the team to validate structure up front. That means the most important step is usually not upload. It is field mapping. Simple version: getting a file in is easy; getting the columns right is what makes it useful.What teams should validate carefully
- email fields
- phone fields
- contact names
- timezone values
- whether this source is a one-time load or should later be replaced with a recurring sync
When file imports are the best choice
Choose file imports when:- you need the fastest initial path
- the source system is messy or temporary
- the team wants to validate contact shape before investing in a deeper integration
Common mistakes
- assuming upload success means mapping success
- importing a full dataset before validating a small sample
- forgetting whether the file import is meant to be temporary or permanent
- blaming campaigns before checking import quality