Server Setup
Make sure you have the following information ready:
- Server address and credentials: the hostname or IP address, username, and password or SSH key for your SFTP server (skip this if you plan to use eCourtDate's Managed Infrastructure option, the simplest path for agencies that don't operate their own SFTP server)
- Directory to monitor: the folder path on the remote server where your case management system places export files
- An Upload Template: determines how file columns map to eCourtDate fields (you can create one during setup)
Setting up SFTP is a three-step process: create a server connection, create one or more SFTP Profiles, and enable Auto-Sync.
Step 1: Create a Server
Navigate to Console > SFTPs > Add Server and choose one of the three server types below.
SFTP Server
Connect to an existing SFTP server that your agency manages.
| Field | Description |
|---|---|
| Server Name | A friendly label for this connection. |
| Host / IP | The hostname or IP address of the SFTP server. |
| Username | The login username on the remote server. |
| Password or SSH Private Key | Provide either a password or paste the contents of your SSH private key. See Authentication for key setup. |
| Port | The SSH port. Default: 22. |
| Timeout | Connection timeout in seconds. Default: 10. |
| Directory | The root directory on the remote server to monitor. |
S3 Bucket
Connect to an Amazon S3-compatible storage bucket.
| Field | Description |
|---|---|
| S3 Host | The S3 endpoint (e.g., s3.amazonaws.com). |
| Bucket Name | The name of the S3 bucket. |
| Region | The AWS region where the bucket is hosted (e.g., us-east-1). |
| Access Key | The IAM access key ID. |
| Secret Key | The IAM secret access key. |
| Path | An optional prefix/path within the bucket to monitor. |
The IAM user or role must have the following permissions on the bucket:
s3:ListBuckets3:GetObjects3:PutObjects3:DeleteObject(optional: required only if Delete File After Upload is enabled)
Managed Infrastructure
eCourtDate provisions a dedicated SFTP server hosted on AWS GovCloud on behalf of your agency. This option is ideal for agencies that do not operate their own SFTP infrastructure.
Note: Allow 1 business day for the eCourtDate team to complete provisioning after you submit a Managed Infrastructure request.
Step 2: Create an SFTP Profile
After the server is created, add one or more SFTP Profiles to define how files are discovered and processed.
| Field | Description |
|---|---|
| Source Directory | The directory on the remote server to monitor for new files. |
| Upload Template | The Upload Template that maps file columns to eCourtDate fields. |
| Filename Keyword | An include filter. Only files whose name contains this keyword are picked up by this profile. |
| Blockword | An exclude filter. Files whose name contains this word are skipped. |
| Max Files per Upload | The maximum number of files to process in a single sync cycle. |
| Delete File After Upload | When enabled, the source file is removed from the remote server after successful processing. |
You can create multiple profiles per server to route different file types to different Upload Templates. See Directory Structure for recommended layouts.
Step 3: Enable Auto-Sync
Toggle Auto-Sync Enabled on the server record. When enabled, eCourtDate checks the remote server once per hour for new files that match your SFTP Profile criteria.
After enabling Auto-Sync:
- Upload a test file to the source directory.
- Wait for the next sync cycle (up to one hour).
- Verify the file appears in the Files list on the server detail page in the Console.
- Check the corresponding Upload for processing results.
See Auto-Sync & Downloads for recommended scheduling practices.
Need help? Visit the Help Center.