Who can use this feature?
Available on:
All Culture Amp subscriptions.
You can automate your employee data imports by configuring your HRIS to send files to Culture Amp via Secure File Transfer Protocol (SFTP). This ensures your employee list and demographics are kept up-to-date without manual uploads.
Data Flow: Employee Data flows from your HRIS or external file manager into Culture Amp (one-way sync) as a partial import via SFTP.
Initial Setup Timeframe: The setup time varies by HRIS provider (ranging from 1 week to 6 months). This timeline is largely dependent on your HRIS provider's lead times for enabling automated exports and your IT team's availability to generate secure SSH keys. See the HRIS-Specific Prerequisites section below for details on your provider.
Choosing Your Integration Method
Culture Amp offers three primary ways to connect your employee data. While many organizations use SFTP when a native or API integration is unavailable, some admins prefer it for the granular control it provides over file filtering.
Use the table below to understand how data flows and how deactivations are handled for each method:
Method | Type of Import | Best For | Key Difference |
Full Employee Import | Organizations seeking real-time, daily automation of all employee data that the integration supports. | Data transfer is fully automated. If a user is removed from the HRIS entirely (without an End Date), they are automatically marked as a former user, with their End Date set to the day before the import. | |
Full Employee Import | Organizations seeking real-time, daily automation of all employee data that the integration supports. | Users with an End Date in the HRIS become former employee instantly. For most platforms (except SAP SuccessFactors), users removed without an End Date stay "Active" until a manual sync is performed by Culture Amp Support. | |
SFTP (Secure File Transfer Protocol) | Partial Employee Import | Organizations requiring manual control over file creation or highly unique filtering requirements. | You generate a data file and securely transfer it to Culture Amp at scheduled intervals. Unlike the native integration, users missing from an SFTP file are ignored (staying "Active"). Only Users with an explicit End Date in the file are deactivated as former employees. |
SFTP Checklist
Use this checklist to navigate the SFTP setup. Each step links to a more detailed section below.
Before You Start: Access Requirements
Setting up an SFTP integration involves a technical handshake between your HRIS and Culture Amp. Before you begin, review these core requirements to ensure your data and network are compatible.
Access & Permissions
Access & Permissions
Role | Required Access | Rationale |
Culture Amp Admin | To access Integration settings and save the SSH Public Key. | |
HRIS Admin | Reporting/Integration Admin | To schedule automated exports and configure destination settings. |
IT Specialist | Network/Security Specialist | To generate OpenSSH keys and configure firewalls (Port 22). |
General SFTP Strategic Considerations & Data Logic
General SFTP Strategic Considerations & Data Logic
SFTP Compatibility: If your HRIS isn't listed below or in Culture Amp as a custom SFTP option, contact your HRIS representative. They can confirm if their system supports generating files that align with our employee data template and if there are any associated third-party costs.
Write-Only Security: Our SFTP server is "write-only." Even if a private key were compromised, no data can be downloaded or read from the server by external parties.
Partial Import Logic: SFTP uses "Partial Import" logic. If a user is missing from your file, they are ignored, not deactivated.
Deactivation Requirement: To deactivate a user, they must be present in the file with an End Date specified.
Format Constraints: Use CSV (UTF-8) or XLSX. Standard XLS or "CSV (Macintosh)" may cause encoding errors.
Command Restrictions: Our server only allows the "PUT" command. Actions like RENAME, MOVE, or DELETE will cause the connection to be refused.
Sync Frequency & Naming: We scan for files every 10 minutes. If you send two files with the same name within 15 minutes, the second will fail. We recommend adding a timestamp to your filename.
Field Mapping: Demographic field mapping is not available for SFTP. We will ingest the exact data included on the file that is transferred.
HRIS-Specific Prerequisites & Lead Times
HRIS-Specific Prerequisites & Lead Times
The complexity and lead time for SFTP depend heavily on your specific HRIS provider.
HRIS | Estimated Lead Time | Unique Prerequisites |
Paylocity | 3–6 Months | High-Touch: You cannot build the Custom HR & Payroll report yourself; a Paylocity analyst must create it. Requires a Letter of Intent and a PADE request. Email service@paylocity.com to initiate. Paylocity takes 2–12 weeks to fix spelling/capitalization errors in a report, so ensure the core mapping is 100% correct during the initial technical discovery call with their team. It also requires Strict IP whitelisting and a preference for Windows-format (.ppk) SSH keys. |
ADP (Workforce Now) | 2–4 Weeks | Often requires a paid service request for ADP’s assistance in creating the custom export report. |
HiBob | 2–4 Weeks | Formatting: Rename "Termination Date" to Dates: Must be ISO 8601 ( Language: HiBob does not have a native Language field; you must create a custom field (do not use "Nationality"). SSH Key: Ensure the key pair is generated without a passphrase. |
Rippling | 1–2 Weeks | Regional Availability: Best supported for US Data Center customers. Non-US customers should use the "Other Integration Options" tile. Setup Path: Start by adding Culture Amp from the Rippling App Shop. |
People HR | 2–4 Weeks | Plan Requirement: Requires Professional edition or higher and the SFTP Exporter plugin. Field Constraints: People HR cannot rename default fields or change date formats. Authentication: The SFTP password field must be set to |
TriNet | 1–2 Weeks | Pre-built Template: Use the "Culture Amp Export" found in Key Generation: You can generate and download the Public Key directly from the TriNet "Schedule Report" interface and upload it to Culture Amp. |
UKG | Varies | Mandatory Representative: A UKG representative must work with you to handle the SSH key generation and connection. Encoding: Ensure the export is set to CSV UTF-8. UKG's default ISO-8859-1 encoding is not supported and will cause character errors. |
SAP Successfactors | Varies | Reach out to your representative for lead times regarding custom report generation. |
Step 1. Prepare Your Data File
The first step is to create a report in your HRIS (or external file manager like Filezilla if not using an HRIS) containing all employees and demographics you wish to sync to Culture Amp. We recommend using our Employee Data File Template.
File Format: Must be set to CSV (UTF-8) or XLSX. For UKG users, specifically verify with your rep that the file is not using ISO-8859-1 encoding.
No Compression: Do not ZIP or compress the file. Our server expects the raw data file.
Column Headers: Use the exact column headers listed below. Note that headers are case-sensitive (e.g., "end date" and "End Date" are treated as different demographics).
Encryption (Optional): If using PGP encryption, ensure the file extension is updated to
.csv.pgpor.xlsx.pgp. (see further details below).
🔐 PGP Encryption (Optional)
🔐 PGP Encryption (Optional)
Culture Amp supports PGP encryption for organizations that require an extra layer of security for sensitive files.
Technical Requirements:
Encryption Type: We only accept files encrypted without signing. Signed files will fail ingestion.
Accepted Extensions: Files must be renamed to
<filename>.csv.pgpor<filename>.xlsx.pgp.Encoding:
.csvfiles must be UTF-8 encodedSoftware: Use GnuPG version 2.2.8 or higher.
How to Implement:
Request the Key: Contact Culture Amp Support (reply "Ask a Person" in a support conversation) to retrieve our Public RSA key and recipient email.
Encrypt the File:
Linux:
gpg --encrypt --output <filename>.csv.pgp --armor --recipient <email> <filename>.csv.Windows: Refer to the Microsoft standard PGP activities guide.
Verify: A correctly encrypted file is "ASCII armored" and will look like a block of human-readable text starting with
-----BEGIN PGP MESSAGE-----. In contrast, a signed file is a binary file that will appear as "nonsense" characters or unreadable symbols when opened.
Encrypted file example:
What happens to my files after upload?
Successful Files: Files that process successfully are deleted promptly after ingestion.
Failed Files: Files with incorrect extensions or encryption (like signed files) are moved to a
failed_filesfolder and deleted after 5 days.Retention Policy: All files are automatically removed from our SFTP server within five (5) days.
Tip: Need more info? Access some further PGP documentation, including visual examples, here.
Core Demographics: Field & Data Requirements
To unlock essential features like age/tenure banding and multi-language support, ensure your SFTP file uses the exact column headers listed below.
Column Header (Exact) | Requirement | Platform Benefit |
Name | Required: Use the format: | Primary way to address employees within the platform/various features. |
Preferred Name | Optional. Provides a more personalized experience for employees. | Used for survey and cycle communications. |
Employee Id | Required for People Analytics: A Unique Employee Identifier. Acts as a "double-lock" with Email to prevent duplicate records if an email changes. | Recommended for matching records if an employee's email address changes in your HRIS. |
Required for Performance: A Unique Employee Identifier. Strongly recommended for all users to enable survey invites and platform access. | The primary way employees receive Culture Amp communications. | |
Date of Birth | Recommended. Format as | Unlocks Age banding across your survey reports. |
Start Date | Required for Retention Insights and People Analytics: Format as | Unlocks Tenure banding and reporting. |
End Date | Required: Format as | Essential: The only way to automate deactivations. |
Language | Recommended: Use the appropriate two-letter System Code (e.g., | Sets the employee’s preferred platform language (default is US English). |
Manager Email (Work Email of referenced Manager) | Required for Performance & 1-on-1s: Provide the manager's work email. Leave blank for the top-level leader (e.g., CEO). For most syncs, all email values must be in lower-case.
If you have an existing hierarchy, this column header must match your validated title verbatim. | The Hierarchy Anchor: Automatically builds your org hierarchy for leader-based reporting and performance tools. See additional information below. |
Manager Email header must match your account's validated hierarchy title verbatim. If you have already validated your hierarchy as "Supervisor Email" or use Manager ID as an example, you must use that exact title in your SFTP file.
Managing Your Organizational Hierarchy
Managing Your Organizational Hierarchy
To unlock leader-based reporting, performance cycles, and 1-on-1 conversations, your SFTP file must include a unique manager identifier to build an organizational hierarchy.
Note: You cannot set up a hierarchy for the first time using only an SFTP sync. To activate hierarchy validations, you must first complete one manual CSV/XLSX Full Import.
Confirming Your Hierarchy Path
The steps to finalize your hierarchy depend on whether your account hierarchy has been validated previously:
Path | Essential Action | Why? |
New Hierarchy | Perform a One-Time Manual Full Import | This triggers the "Select Manager Identifier" and "Select Organizational Leader" screens, which are not available via SFTP. |
Existing Hierarchy | Verbatim Header Match | SFTP will only update the hierarchy automatically if the column header matches your current hierarchy demographic (e.g., Manager Email) exactly. |
Hierarchy Data Requirements
To ensure a smooth validation (whether manual or via SFTP), your data must follow this logic:
Identifier Type: Use Manager Email (recommended) or Manager ID. You cannot validate or sync a hierarchy based on Manager Name.
The "Double Match": The value in your manager identifier column must match an existing employee's Email or ID in Culture Amp.
Top Leader: Leave the manager field blank for your organizational leader (e.g., CEO) to establish the top of the tree.
Verification: To see if your hierarchy is active, go to Settings > Demographics and look for the Hierarchy icon (three connected nodes) next to your manager field.
Step 2: Generate an SSH Key Pair
Culture Amp uses SSH Key Pair authentication to ensure your data transfer is unique and secure. This consists of a Public Key (which you upload to Culture Amp) and a Private Key (which stays with your HRIS or IT team).
Determine Your Key Source
Before you open a command terminal, check if your HRIS handles this for you.
If you use... | Action Required |
ADP, SAP, or UKG | Request the Public Key from your HRIS representative. They manage the keys for you. Skip to Step 3. |
TriNet | Download the Key directly from the TriNet "Schedule Report" interface. Open it in a text editor (like Notepad) to copy the string. Skip to Step 3. |
Paylocity | High-Touch Setup: You must provide Paylocity with a Private Key in .ppk format. See the Paylocity conversion note below. |
All Others | Generate your own keys using the instructions in the "Do It Yourself" section below. |
"Do It Yourself" Manual SSH Key Generation
If your HRIS does not provide a key, your IT department should generate one using a command-line tool.
Technical Requirements
Format: We only support OpenSSH key pairs.
Unsupported: SSH2 is not supported. If your tool generates keys in SSH2 format (starting with
---- BEGIN SSH2 ----) they must be converted before use.HiBob Users: You must leave the passphrase blank; HiBob does not support passphrases for automated exports.
🔑 Generate & Locate Your Keys
🔑 Generate & Locate Your Keys
If your HRIS does not provide a key, your IT department should generate one using a command-line tool.
Check Tools: Ensure you have
ssh-keygeninstalled (standard on Mac/Linux) or use PuTTYgen for Windows.For a full walkthrough on installing and using PuTTY on Windows, see the PuTTY Home & Key Generation Guide.
Run Command: Run
ssh-keygen -t rsa -b 4096.Save Location: When prompted, enter a file path and filename (e.g.,
cultureamp_sftp_key). We recommend creating a new folder to avoid overwriting existing keys.Passphrase (Optional): You may enter a passphrase for added security, though it is not compulsory. Note: HiBob does not support passphrases for automated exports.
Once generated, navigate to the folder where you saved the files:
Public Key: Usually ends in
.pub. Open this with a text editor to copy the string starting withssh-rsa(This key will later be saved in Culture Amp)Private Key: This file has no extension or ends in
.pem/.key. Do not share this key via email or insecure means (this key remains with your HRIS
🎥 Video Tutorials: How to generate keys
🎥 Video Tutorials: How to generate keys
Specialized Conversions (Paylocity Users)
Specialized Conversions (Paylocity Users)
Sometimes the keys you have aren't in the right format for the "handshake."
Paylocity requires a Windows-style Private Key.
Windows: Use PuTTYgen to save your private key as a
.ppk.Mac/Linux: Use
brew install puttygento convert your key:puttygen -t rsa -b 4096 -C "email@co.com" -o private_key.ppkThe Workflow: Send the .ppk Private Key to Paylocity and upload the OpenSSH Public Key to Culture Amp.
Converting SSH2 to OpenSSH Key Format
Converting SSH2 to OpenSSH Key Format
If your HRIS generates keys in SSH2 format, run the following command to convert the public key for Culture Amp: ssh-keygen -i -f ssh2_key.pub > openssh_key.pub
Tip: Some HRIS clients may generate the SSH Key Pair on your behalf. It's best to check with them directly if this is something they offer.
Step 3: Configure the SFTP Connection in Culture Amp
Once you've generated your SSH key pair, you're ready to configure the SFTP integration in Culture Amp. This is where you will enter your Public SSH Key and gather other required information to finalize the setup.
Navigate to Account > Integrations.
Click Other Integration Options
Note: Even if you see a specific tile for your HRIS (e.g., ADP), do not select it for SFTP. Those tiles are reserved for Native API integrations. Exception: Rippling US customers may be directed to use the Rippling-specific tile as part of the App Shop setup.
Enter your Public SSH Key into the provided text box. Ensure you copy the entire string, typically starting with
ssh-rsa.Select a Technical Point of Contact. This administrator will receive automated email notifications regarding sync status, import blocks, or connection errors.
Click Save.
Gather Credentials: On the following screen, copy and save the Host/Hostname and Username. You will need these specific credentials to configure the "handshake" in your HRIS in the next step.
Step 4: Configure the SFTP Connection in Your HRIS
After saving your SFTP connection within Culture Amp, you will need to provide the following details (collected in Step 3) to your HRIS. This ensures the two systems can authenticate once the file transfer is triggered.
Protocol: SFTP (Port 22)
Hostname: Copy text from the Culture Amp Data Integrations page.
Username: Copy text from the Culture Amp Data Integrations page.
Logon Type: Key File (This ensures the client uses your Private Key for authentication rather than a password).
Authentication: Upload your Private Key (not the public key you entered in Culture amp.
Directory/Path: Root (leave blank or use a single forward slash
/).
Once these details are saved in your HRIS, you can schedule the report to be sent to Culture Amp on a regular, automated basis.
Note: The hostname and username are case-sensitive. Always copy them directly from the Data Integrations page to avoid connection errors.
FileZilla: Specific Instructions
FileZilla: Specific Instructions
If you are using FileZilla to manage your transfers, follow these specific settings to ensure compatibility with Culture Amp’s requirements:
Open Site Manager: Go to File > Site Manager.
Protocol: Select SFTP - SSH File Transfer Protocol.
Logon Type: Select Key File.
User: Enter the Username from your Culture Amp Data Integrations page.
Key File: Click Browse and select the Private Key you generated in Step 2.
Connect: Click Connect. If prompted to trust the host key, select Always trust this host.
Here's a video example of how to connect to SFTP Using Filezilla. The steps provided in this video may vary slightly dependant on your specific environment, tools, or software versions.
For a deep dive into FileZilla’s advanced key management (including SSH-agent setup and Mac-specific shortcuts), refer to the FileZilla Wiki: Key-based Authentication Guide.
Step 5: Test Your Data & Connection
Before enabling a recurring schedule, we recommend verifying both your data formatting and your secure connection.
Test Your SFTP Connection
To confirm your connection is successful without altering your employee data, you can send a "dummy" file:
Upload a file in
.txtformat via your SFTP client.A successful transfer of a
.txtfile confirms the connection is active but will not trigger a data import.
Test Your Data Formatting
Since SFTP imports follow the same requirements as manual imports, you can pre-validate your file structure within the platform:
Export the data report you intend to send via SFTP
Navigate to Settings > Employee Data > Users > Import & Export > Manual Import.
Select Partial Import and upload your file.
Proceed to the "Review Import Summary" stage. This allows you to review how the data affects your users (added, updated, or demographics) without saving any changes.
Simply exit the screen after reviewing the summary if you are not ready to apply the data.
Troubleshooting & FAQs
General Data Integrity & Import Management
The first step when investigating any data issue is to check the Import Summary Screen for your most recent import.
Go to Settings > Employee Data > Import History.
Select your most recent import to view details.
This screen provides information on the state of your integration, any specific errors, or will prompt you to run a manual sync to identify problems.
Common SFTP Errors
Common SFTP Errors
Error Message | Possible Cause | Recommended Solution |
Access Denied | Incorrect SSH Key Format: The uploaded key is not in the required OpenSSH format (e.g., SSH2 or SSH-1 (RSA)). | Ensure your public key is in OpenSSH format. You can check this in Settings > Data Integrations, where the platform outlines the key type. If needed, use a terminal to convert the key using |
Incorrect Folder Path: You may be trying to upload to a specific sub-folder (like | The upload must be sent to the root directory. Leave the destination folder blank or set it to | |
Command Restrictions: Culture Amp only supports the "PUT" command. | We do not support "Write", "Delete", "Get", "Move", "Open", or "Rename" commands. Ensure your client is configured to upload directly without attempting to modify or list files on our server. | |
Client-Specific Settings: Some clients (like WinSCP) automatically try to "preserve timestamps" or "set permissions" after a transfer. | Disable "Preserve timestamp" or "Set permissions" in your client settings. Alternatively, enable the "Ignore permission errors" option. | |
Duplicate File Name: You are sending a file with a name that was used within the last 15 minutes. | Our servers scan for new files every 10 minutes, but a 15-minute buffer is required before reusing a filename. If you send multiple files with the identical name within this window, the second file will fail. There is no cap on how many changes can be processed in a single import; however, to send multiple separate files in short succession, you must use unique filenames. Add a unique time-stamp to your file name to differentiate each upload. | |
File is Locked: The file matches a name currently "stuck" in our system and cannot be overwritten. | Add a unique timestamp to every filename (e.g., | |
People HR Authentication Failed: Check password details | Double-check that your Password in the People HR SFTP Exporter is set to a single forward slash (/) and that your private key is correctly uploaded within the plugin. | |
Access Denied (during transfer) | Temporary Filenames: Some clients (e.g., WinSCP) upload files with a | Culture Amp does not support the RENAME command. Disable "Transfer to temporary filename" or "Resume support" in your SFTP client settings to send the file in one action. |
Connection Refused | Firewall Blocking: Your internal network or local firewall is blocking the connection. | Have your IT team allow outbound access via the hostname (not a specific IP) on TCP Port 22. |
Credential Mismatch: Hostname or username typos. | Copy these directly from the Culture Amp setup form; both are case-sensitive. | |
Private key file error | Invalid Private Key Format | If your key starts with |
Incorrect File Format / Missing Header | Formatting or Delimiters: The file is not CSV (UTF-8) or uses a delimiter other than a comma (e.g., a semicolon). | Ensure the file is CSV (UTF-8) with comma delimiters. Use a text editor to verify these settings. UTF-8 is required to ensure special characters are formatted correctly. |
Layout Issues: The first row does not correctly list the required demographic headers. | Verify the layout matches your platform's requirements. Try a manual partial import to confirm the file structure is accepted without saving changes. | |
Improper Quoting / Illegal Quoting: Mismatched quotes, brackets, or unescaped commas in a CSV file. | Review the file in a text editor. Ensure values containing commas are wrapped in quotes. Alternatively, switch to XLSX to avoid CSV parsing errors | |
Import attempt not showing | Missing Mandatory Columns or Data Issues: Missing mandatory columns (e.g., Employee Id, Email) or data issues like duplicate email addresses. | Ensure your file includes all mandatory columns. Review the file for data issues, such as duplicate emails, and verify that the file is not corrupted. |
Unexpected Server Shutdown | Unsupported Protocol version | Ensure your SFTP client is using SFTP version 4, 5, or 6. Versions 0, 1, and 2 are not supported. |
Unprocessable Entity (422) | Data Validation Error: The connection is successful, but the data inside the file has errors. | Check your SFTP client's Event Log or Payload. It will pinpoint the exact field (like "duplicate-email") causing the rejection. |
Tip: If your upload is successful but the data doesn't appear in Culture Amp, check your SFTP client's Event Log for a "Payload" or "422 Unprocessable Entity" error. This log usually contains a text snippet identifying the exact row and field (e.g., a specific duplicate email) that caused the record to be rejected.
Handling Duplicate Employees
Handling Duplicate Employees
Culture Amp uses two fields as unique identifiers for user profiles: Email and Employee ID.
As long as at least one of these remains consistent between your SFTP report and Culture Amp, the sync will successfully update the existing profile rather than creating a new one.
Duplicate Risk: If you change both the Email and the Employee ID simultaneously on your SFTP report, the sync will not find a match and will create a duplicate profile.
If you see a duplicate profile error flag during your import, take the following steps:
Scenario | Action to Take |
A. Before Changes Are Applied | During the first sync review screen, stop the sync. Update the employee emails in Culture Amp to match those on your SFTP report.
|
B. After Changes Are Applied | To clean up the duplicated profiles:
|
Further Guidance | Check out our dedicated support guide for further information on duplicate employee clean-up. |
Handling Terminated Employees
Handling Terminated Employees
When removing users from the platform, you have two options: you can mark them as inactive, indicating they are former employees with an end date, or deactivate them, with no specified end date. Both options result in the user being made inactive.
Learn more about the differences between former and deactivated employees here.
Mark Users Inactive as Former Employees:
To make users inactive via SFTP as former employees:
Ensure that there is an End Date column included in your user file
Apply an End Date value next to the employee you are deactivating
Following your update, the Culture Amp platform generally does a file sweep every 10 minutes or so and will process any file that has been picked up and process the updates to the platform.
Once the import is processed, those users will show up under your Settings > Users page under the Former User list.
Mark Users Inactive as Deactivated Employees:
Ensure that your SFTP file has an End Date column
Under the End Date column, ensure that the value for the user you would like to deactivate is blank.
Create an Employee Deactivated column in your SFTP file. Important: This column must be placed before any custom/other demographics in your file layout.
Assign TRUE as the value next to the employee/s you are deactivating.
Make sure FALSE is set for any other employees.
Following your update, the Culture Amp platform generally does a file sweep every 10 minutes or so and will process any file that has been picked up and process the updates to the platform.
Once the import is processed, those users will show up under your Settings > Users page under the Deactivated User list.
Alternatively, you can mark users as inactive by deactivating them individually in the platform. Follow the instructions provided here.
Just make sure that once you manually deactivate these users, they are removed from any file uploads moving forward.
Sync Blocked to Protect Employee Privacy
Sync Blocked to Protect Employee Privacy
Your upload may be blocked if Culture Amp detects a high-risk change for an employee. You will receive an email notification if this occurs.
When It Happens: The sync is blocked if a combination of an employee's Name, Date of Birth, or Email is changed simultaneously.
Purpose: This prevents one employee from accidentally getting access to another employee's private information (like performance reviews).
Fix: If you've intentionally changed the employee's details, you can run a one-time manual Partial Import to bypass the block and verify the identity update.
Switching to the New Hostname (Legacy Integration Fix)
Switching to the New Hostname (Legacy Integration Fix)
If a previously working SFTP connection stops, you may need to update to our current hostname (starting with "secure." rather than "sftp.").
Navigate to Settings > Account > Integrations.
Copy your existing Public SSH Key to a temporary text file.
Delete the existing integration via Configure Integration > Delete.
Re-create the integration supplying the same Public Key.
Update your HRIS/SFTP client with the new Hostname. Ensure the new hostname begins with “secure.” rather than “sftp.” and the target directory is set to “/”.
SFTP FAQs
SFTP FAQs
Question | Answer |
How do I pause the SFTP integration? | SFTP integrations cannot be paused within Culture Amp. You must contact your HRIS or file provider to stop the automated export. Because the sync frequency is controlled entirely on their end, Culture Amp cannot pause the incoming data for you. |
Can we set up SFTP with two different HRIS clients? | Yes. You can have two different systems send files as partial imports. However, Culture Amp only supports one Public Key at a time; you must use the same key pair for both HRIS clients. |
Can I combine SFTP with a Native Integration? | No. This "multi-source" setup is only possible between two SFTP connections. You cannot run two native integrations simultaneously (e.g., Workday and BambooHR), nor can you combine a native integration with an SFTP sync. |
💬 Need help? Just reply with "Ask a Person" in a Support Conversation to speak with a Product Support Specialist.