---
title: "FTP data sync file requirements"
slug: "ftp-data-sync-technical-specs"
description: "Sync signature data by FTP from a source Opensense doesn't integrate with: the CSV file must be UTF-8, comma-delimited, with lowercase headers and emails."
updated: 2024-01-14T01:25:32.000Z
canonical: "https://help.opensense.com/docs/ftp-data-sync-technical-specs"
---

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

# FTP data sync file requirements

## Overview

Company email signatures need a source for the data that goes into each sender's signature. If you use a directory that Opensense doesn't integrate with natively, Opensense can still sync your employees' signature field data from any data source, using **File Transfer Protocol (FTP)**. Opensense can connect to your FTP server, or you can use ours.

## File requirements

To avoid issues with employee data synced by FTP, the file must be:

1. A CSV file in UTF-8 format
2. Comma-delimited
3. With lowercase column headers that match the merge fields in your email signature, for example `name`, `title`, `phone`, `mobile`, and `email`
4. With a column of lowercase email addresses

## What's next

- [Syncing users from a CSV file (classic UI)](https://help.opensense.com/docs/manual-sync-of-a-csv-file): the same CSV format, uploaded by hand.
- [Field data priority](https://help.opensense.com/docs/field-data-priority)