Migrating from Fivetran Email
Move Fivetran Email connectors to DLH.io Email (Source) File Ingest
Each Fivetran Email connector maps to one DLH.io Email (Source) File Ingest connection.
Before you migrate
Check whether the sending system has an API. Replacing an emailed report with a direct DLH.io connector removes the dependency on someone's mailbox. Browse connectors, or ask our team about building one with the DLH.io SDK.
Then record these settings from each Fivetran connector so the DLH.io connection and any downstream models can match them:
| Fivetran setting | Why it matters |
|---|---|
| Destination schema and table | Becomes the Target Schema Prefix and table in your destination |
| File type and file pattern | DLH.io supports CSV, XLS and XLSX attachments |
| Delimiter, quote character, header and skip rows | Confirms the files will parse the same way |
Load mode (append_file or upsert_file) | Append keeps every file's rows; downstream models that pick the latest file depend on this |
Fivetran metadata columns (_file, _line, _modified) | Models that filter on these columns need to be updated after cutover |
Recommended cutover
- Create the DLH.io connection and note its inbound address.
- Have the sender, or a mailbox rule, send to both the Fivetran and DLH.io addresses for one or two delivery cycles.
- Compare row counts per file between the two tables.
- Update downstream models that reference Fivetran metadata columns.
- Remove the Fivetran address from the sender and pause the Fivetran connector.