If your organization is using EverTrue's Data Manager Platform or Console to import files, review this article to understand necessary naming conventions. Please note these instructions apply to automated customers. If your organization is not using automation, this may be skipped!

If you haven’t set up your SFTP workflow, reach out to genius@evertrue.com. Once you establish a secure connection, you can drop the files in the uploads folder.

Naming Conventions for Data Manager Importer

Naming Standard Files

Specific naming conventions must be followed for standard files to be processed correctly. The first time you upload a new file type, you are required to go through the mapping process on data.evertrue.com. The following uploads will automatically identify your file type and save your previous mapping. 

Please note some additional insights regarding SFTP standard file naming conventions for Data Manager Platform imports:

• If the above rules are not followed, all other imports are assumed to be a Constituents file type.
• The Full/Partial import naming convention defaults the file type to partial. Ensure that you add ".full" to identify a full import.

Naming Micro Files

Specific naming conventions must be followed for micro files to be processed correctly. As with standard files, the first time you upload a new micro file type, you are required to go through the mapping process on data.evertrue.com. The following uploads will automatically identify your file type and save your previous mapping.

---

Naming Conventions for Console Importer

In order for your files to be correctly read by EverTrue's Console, you will need to use specific file types and naming conventions when importing. For SFTP transfers, EverTrue supports CSV files ending in ".csv" and CSVs compressed in either ZIP formats (ending in ".csv.zip") or GZIP formats (ending in ".csv.gz"). As an example, myorg.2012-07-02.csv.zip would be an appropriate compressed CSV file type.

Imports will default to standard imports if specific naming conventions are not used. Please take a moment to review the naming conventions required to specify import types.

• Full Import: Use the keyword ".full." before the file extension (e.g. myorg-2015-12-01.full.csv).
• RM Assignment Import: Use the keyword ".solicitors." before the file extension. (e.g. myorg-2015-12-01.solicitors.csv).
• Interactions Files (notes or contact reports): Use the keyword ".interactions." before the file extension (e.g. myorgnotes-2015-8-10.interactions.csv).
• Proposals File: Use the keyword ".proposals." before the file extension. (e.g. ourproposals-2018.proposals.csv).
• Transactional Gifts: Use the keyword ".gifts." before the file extension. (e.g. myorggifts-2015-12-01.gifts.csv).
• Volunteer Assignment File: Use the keyword ".assignments." before the file extension. (e.g. myorgvols-2015-12-01.assignments.csv).

Please keep in mind some additional insights regarding SFTP file naming conventions for Console:

• You may combine the outlined keywords in any order to specify a full interaction, proposal, or transactional gift file (e.g. myorgnotes-2015-8-10.interactions.full.csv or myorgnotes-2015-8-10.full.interactions.csv).
• Constituent files do not require a particular naming convention.
• We recommend using a consistent naming scheme that creates a unique filename containing the data of the export for each new file uploaded. This filename is recorded in the import history. 

---

For any other questions reach out to EverTrue Support at genius@evertrue.com.