GlobalSCAPE Knowledge Base

Importing User Accounts from Legacy Systems into EFT

Karla Marsh


  • EFT v6 -


Suppose you have purchased and installed Globalscape EFT, it has been configured with a Site and is fully functional. The customer has existing users that need to be migrated from the legacy file transfer solution. The user accounts have encrypted passwords that must continue to work after they have been migrated.

To provide access to legacy user account information, the customer has exported the usernames with encrypted password. The user data is stored in a flat file.

Importing User Accounts into EFT:

User accounts can be imported into EFT using the Globalscape Migration Tool. The user data will be formatted in XML for the import. The import will be a manual process requiring Admin access to the command line on the EFT.

Please refer to the EFTUtils-Help.rtf included with the Migration Tool for detailed configuration and usage information.

Migration Tool Prerequisites:

  • EFT Server development server
  • EFT Server production server
  • SFTPCOMInterface API registered
  • .NET framework 4.0 installed

Preparing to Use the Migration Tool:

You must allow remote Admin access to your EFT admin console. Ensure that your Sync Admin account has COM access. Refer to "Allowing Remote Admin Access" in the EFT help documentation.-

EFT utilities command line tool uses a single configuration named eftutils.exe.config in XML format.

Edit the section below in eftutils.exe.config with information specific to your EFT.

The connectionStrings section contains three connections strings used by the tool. (For this example, we will only use the first connection option.)

EFTUtils.Properties.Settings.EFTServerConnectionString - Main EFT Server connection string used to connect EFT Server using COM API. The information needed for this configuration was configured in the previous step in the Server Administration tab.

<add name="EFTUtils.Properties.Settings.EFTServerConnectionString" connectionString="Server=localhost;Port=1100;UserID=admin;Password=admin;Integrated Security=False" />

Also, be sure to double check the location of your AUD file. Globalscape Authentication does not rely on outside sources for user information. All information in the authentication database is protected from the operating system, contained within the .aud file located in EFT data folder (e.g., C:\ProgramData\Globalscape\EFT Enterprise). The data is encrypted and can only be modified through the administration interface. If you haven't used the default paths during installation, the AUD file could be in a different location. If so, search eftutils.exe.config for the AUD Settings section and update the AUD path with your actual configuration location.

<!-- Source AUD Path exception - Path where AUD file is located for source

Possible uses:

Path where AUD file is located for destination -->

<value>C:\ProgramData\GlobalSCAPE\EFT Server Enterprise\MySite.aud</value>


<setting name="FilterOperator" serializeAs="String">



<setting name="AuthenticationProviderPath1" serializeAs="String">

<!-- AUD Path exception - Path used by sync action only when Users are sync used to extract passwords hashed from the AUD file.

Possible uses:

Path where AUD file is located for destination -->

<value>C:\ProgramData\GlobalSCAPE\EFT Server Enterprise\MySite1.aud</value>


You will need to change the "ImportPasswordType" value to Literal.

<setting name="ImportPasswordType" serializeAs="String"> <value>Literal</value>

**If the eftutils.exe.config file does not contain the proper account access, password type and location of your AUD file this process will fail. **

Preparing the XML for User Import:

The import process requires XML to store the user account information for the import. The Globalscape Professional Services can provide this XML template or you can generate one with the process described below.

To generate the XML file required for the import, you must create, then export a new EFT user. (Refer to Creating a User Account, if necessary.)

Export the user to XML using the Sync Tool and the command shown below. (When launching the CMD prompt be sure to do so as Admin.)

The result will produce a new file in the Sync folder.

This file can now be used as a template to add the usernames and encrypted passwords exported from the legacy system.

With an updated XML template, you can now import the legacy user accounts. To import the legacy user accounts using this template, reverse the export process, by using the command shown below.

eftutils.exe import "USERS" "Mysite" /xml

You should now double check your imported usernames and passwords. You may be required to Sync home folder permissions or other Site-specific attributes.

Last Modified: 2 Years Ago
Last Modified By: kmarsh
Rated 1 star based on 17 votes.
Article has been viewed 28K times.
Also In This Category