Archive import files to your FTP server.
CSVbox accepts CSV and Excel uploads from your users, validates the data, and stores each file on your FTP server in a folder path you configure. Works with any FTP or SFTP destination.
- Validated data only
- Column mapping included
- SOC 2 Type II + GDPR
FTP destinations are common in enterprise, government, and legacy-system integrations where downstream processes — batch jobs, ETL pipelines, partner integrations — consume files from a shared file server.
CSVbox gives users a modern, validated upload UI while preserving the FTP-based file delivery that your downstream systems already expect. Users get an in-app importer experience; your FTP server receives clean, validated files.
How It Works
- 1Configure your FTP destination
In the CSVbox dashboard, add an FTP destination. Provide your FTP host, port, username, and password. Select FTP or SFTP (recommended for security).
- 2Set the folder path
Specify the remote directory where files should be stored. CSVbox generates a unique filename per import (import ID + timestamp + original filename).
- 3Embed and ship
Add the CSVbox widget to your app. Users upload files; validated files are stored in the configured FTP folder.
Configuration Options
| Option | Description |
|---|---|
| Protocol | FTP or SFTP (recommended) |
| Host | FTP server hostname or IP address |
| Port | Default 21 (FTP) or 22 (SFTP) |
| Username | FTP account username |
| Password | FTP account password |
| Remote path | Folder path on the FTP server |
| Filename | Import ID + timestamp (configurable prefix) |
| File format | Original file (CSV/Excel) or re-encoded CSV |
Common Use Cases
Upload validated files to an FTP server consumed by downstream ERP, CRM, or batch processing systems.
Partners upload data files that land on a shared FTP server for pickup by your internal systems.
Archive every import file on a controlled FTP server for audit, record-keeping, or regulatory requirements.
Feed data into legacy systems that only accept file-based input via FTP drop.
Frequently Asked Questions
Is SFTP supported?
Yes. SFTP (SSH File Transfer Protocol) is recommended over FTP for security. Both are supported.
Can I use key-based authentication for SFTP?
Yes. Provide your SFTP private key in the destination configuration instead of a password.
What file format is stored on the FTP server?
By default, the original file is stored. Optionally, CSVbox can re-encode and store the file as clean UTF-8 CSV regardless of the original format.
Can I store files in different folders based on the schema or user?
Yes. Use dynamic path patterns in the remote path configuration (e.g., append the schema ID or import date to the folder path).
Does CSVbox validate data before storing on FTP?
Yes. CSVbox validates every row against your schema rules before writing the file to FTP. Only imports that pass validation produce an FTP file.