iqavaiqava
Sign inGet started

By module

Data Connectors

Bring data in from your own database without exporting spreadsheets. Connect once (read-only), map any table or query to CRM fields, and import on demand or on a schedule.

Best use case

Keeping iqava CRM in step with a system of record you already run — a policy admin system, a legacy CRM, a data warehouse — without manual CSV exports.

A paid add-on

Data Connectors is an optional add-on. An admin enables it from Extensions; it then appears under Distribution & CRM. See pricing.

How it works

Connect (read-only)Map columns → fieldsPreviewImport — now or scheduled

A connection holds an encrypted, read-only credential to your database. An import profile maps a table (or a read-only SELECT) to CRM Account and Contact fields; anything you don't map can be kept as custom fields. Each run pulls the rows and creates clients through the same importer the spreadsheet upload uses — so de-duplication, custom fields and per-row errors all behave identically.

Security model

Connectors are built to be safe to point at a production database:

  • Read-only. Only single SELECT/WITH statements are accepted (no chained statements), and the session is set read-only where the engine supports it — a connector can never write to your database. Use a read-only database user as well.
  • Encrypted at rest. Passwords are encrypted (AES-256-GCM) and never returned to the browser.
  • Tenant-isolated. Connections, profiles and run history are protected by row-level security, like the rest of your data.
  • Bounded. Connection and statement timeouts are capped and every query is row-limited.
  • Audited. Adding, editing, testing and running are all written to the audit trail.

Add a connection

  1. Open Data Connectors
    From Clients & Accounts, choose Data connectors (or the sidebar Extensions group).
  2. Add connection
    Pick the engine — PostgreSQL, MySQL/MariaDB, SQL Server, or Oracle — then enter host, port, database (the service name for Oracle), a read-only username and password, and SSL mode.
  3. Test
    Save, then Test — iqava connects and reports the server version, or the exact error if it can't.

Best practice

Create a dedicated read-only user on your database and, where possible, allow-list iqava's egress address at your firewall. Prefer a read replica over the primary.

Build an import profile

  1. Load the schema
    On a connection, choose New import profile and Load schema to browse tables, or switch to a read-only SELECT.
  2. Map columns
    Pick a table; iqava auto-guesses the mapping from column names. Map the Account name (required) and any Account/Contact fields; keep the rest as custom fields.
  3. Normalise values (optional)
    Per field, apply a transform so data lands the way you want it stored — trim, UPPERCASE, Title Case, digits-only (phones), or dates → YYYY-MM-DD.
  4. Preview
    Preview pulls a handful of sample rows so you can confirm the mapping before importing.
  5. Schedule
    Choose Manual only, Every hour or Every day, then save.

Run & schedule

Run now imports immediately and shows how many clients were created, skipped (blank or duplicate name) and any row errors. Scheduled profiles run automatically in the background; the run history on each profile shows every run with its result. Imports are idempotent — re-running skips accounts whose name already exists, so a schedule keeps CRM current without creating duplicates.

Watch out

A schedule keeps pulling from your database, so scope the source table or query to the rows you actually want in CRM, and disable a profile when you no longer need it.

Documentation overview