---
title: "SFTP in Test Environments"
slug: "sftp-in-test-environments"
updated: 2026-02-16T23:05:32Z
published: 2026-02-16T23:05:32Z
canonical: "knowledge.technolutions.net/sftp-in-test-environments"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# SFTP in Test Environments

## Testing imports and exports from SFTP

To test imports and exports from SFTP in test environments, use the */test* folder and subfolders to test an upload from the SFTP site into a test environment. The subfolders in */test* should mirror the folders used in your production database. For example, if your Common Application files are loaded into */incoming/commonapp* in production, they should be loaded into */test/incoming/commonapp* in test.

A subfolder for */test/outgoing* is created automatically when a scheduled export is manually run from a test environment. A subfolder for */test/incoming* is created automatically when a source format includes this subfolder path as an **Import Path/Mask.** Otherwise, the folder can be created manually.

> 🔔 Important!
> 
> It is not possible to connect directly to a test environment via SFTP. Instead, connect to your production environment and deposit files into the */test* folder. It might be necessary to create that folder (and any subfolders) if it doesn't exist.

## Running file pickup and import manually

Because test environments do not perform scheduled file pickups or imports, when files are dropped off into the */test/incoming* folder or one of its subfolders, you must take the following steps in your test environment. For more information on configuring automated imports from SFTP, review [Scheduling Imports from SFTP](/v1/docs/scheduling-imports-from-sftp).

1. Select **Database** from the main navigation.
2. Under the heading “Import and Data Processing”, click **Force Process Pickup.** ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image-HYL0IPOP.png?sv=2026-02-06&spr=https&st=2026-11-09T11%3A12%3A18Z&se=2026-11-09T12%3A12%3A18Z&sr=c&sp=r&sig=%2BIXlpTJz2FW6jqAz8Dmjg6k50tdyR3I6knSK7sbQT2g%3D)
3. Slate will manually pick up any files from the /test/incoming directory that [match the Import Path / Mask](/v1/docs/source-format-settings#import-pathmask) of an active [Source Format](/v1/docs/source-formats-overview).
4. Once you see the screen say “OK”, the pickup process has run completely.
5. Navigate back to the **Database** view and under the heading “Import and Data Processing”, click **Force Process Import.** ![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/image-VFVK7UOZ.png?sv=2026-02-06&spr=https&st=2026-11-09T11%3A12%3A18Z&se=2026-11-09T12%3A12%3A18Z&sr=c&sp=r&sig=%2BIXlpTJz2FW6jqAz8Dmjg6k50tdyR3I6knSK7sbQT2g%3D)
6. Slate will attempt to import the files to the appropriate Source Format.

> Note
> 
> The following is ***not*** an error message:
> 
> *The IP address is allowed on the firewall, but there have been no connection attempts in the past 24 hours.*
> 
> The IP address used in the validation tool has not yet been used to connect through an SFTP client. Try connecting through the SFTP client first, then utilizing the **connection validation tool** to help troubleshoot any issues.

> Further Reading
> 
> - [Test environments](/v1/docs/test-environments)
> - [Connection validation tool](/v1/docs/sftp-connection-validation)