You import contacts into Stravax Engage by uploading a CSV file, mapping its columns to contact fields, and reviewing a dry-run preview before anything is written. Rows that match an existing contact by phone number update that contact instead of creating a duplicate. You can also export your contact book to CSV at any time.
The import screen suggests a column mapping automatically, matching your file's headers to contact fields and to your organization's custom fields by name. You review and adjust that mapping before running the import. Columns you leave unmapped are simply not imported, that's a mapping choice, not an error.
You can map columns to:
A dry-run runs the exact same validation as a real import but writes nothing. It reports how many rows would be created, how many would update an existing contact, and how many have a problem, with the specific reason listed per row, for example an invalid phone number, a value that isn't one of a picklist's options, or a non-numeric value in a number field.
Because the dry-run and the real import share the same validation, the preview's verdict is binding: running the import for real produces the same created, updated, and invalid counts you saw in the preview.
Phone numbers are normalized to the same format used everywhere else in the product, so an import row matches an existing contact reliably. A row whose phone number already exists in your contact book updates that contact. A row with a new phone number creates a new contact. If the same phone number appears more than once in one file, only the first occurrence counts as new; the rest are treated as the same contact.
Import is rate limited per organization to prevent abuse, and a file is checked against a size and row-count limit before it's parsed, so an oversized file is rejected right away rather than partially processed. If an import would take you over your plan's contact limit, the rows that would exceed it are reported as invalid rather than silently dropped. See current plans for contact limits.
Export downloads your contact book as a CSV file, scoped to your organization only. Exported values are protected against spreadsheet formula injection, so a value starting with a character like = won't run as a formula when you open the file in Excel or Google Sheets.