Glossary
What is an SFTP integration?
An SFTP integration exchanges data between systems as files, typically scheduled CSV exports, over the secure SSH File Transfer Protocol.
An SFTP integration moves data as files instead of API calls. One system exports a file, often CSV, on a schedule and places it on an SFTP server; the other system picks it up, validates it and imports the data. Many enterprise HR and finance systems still offer file exports where APIs are limited or access is restricted.
How does it work?
- The source system generates a scheduled export, for example a daily employee file.
- It uploads the file to an agreed SFTP folder using key-based authentication.
- The receiving job detects the new file, validates columns and row counts, and imports it.
- Processed files are archived, and errors are reported to the owner.
File feeds are slower than APIs, often daily rather than real time, but they are predictable and easy to audit. Many enterprise integrations combine both: a nightly file for the full picture and API calls or webhooks for urgent changes such as terminations.
Where it shows up in integrations
- Enterprise HRIS Some UKG or SAP customers provide employee data as scheduled report files.
- Legacy systems Older on-premise systems with no usable API can still export files.
- Bulk loads Large initial migrations are often easier as files than as millions of API calls.
Common pitfalls
- No validation, so a truncated or reordered file overwrites good data.
- Treating missing employees in a full file as terminations without safeguards.
- Shared passwords instead of SSH keys, and no rotation.
- No alert when the expected file does not arrive.