Overview
Connecting Vergo to Foundation requires three setup steps completed in order: creating a dedicated ODBC user in Foundation, installing two pieces of software (the ODBC Driver and the FSI Importer), and raising a ticket with your IT team to whitelist Vergo's IP addresses. Your Vergo implementation specialist will guide you through this process and confirm the connection is working before you go live.
Before starting, identify whether you are a Foundation Cloud (Hosted) customer or a Foundation On-premise customer — the installation requirements differ between the two.
Step 1: create an ODBC user in Foundation
Vergo connects to Foundation via ODBC. You need to create a dedicated user in Foundation with ODBC access enabled before any sync can happen.
Go to Security in Foundation
Open the Foundation main menu.
Under Tools and System, select Security.
Add the Vergo user
In the Security window, press the + sign next to Foundation Software LLC to expand the tree.
Right-click the Users folder and select Add user...
In the New User window, enter the following details exactly as shown:
User ID: Vergo
Name: Vergo
Password: [Provided by your onboarding manager]
Company No: Your company name
ODBC Access: checked (this is required — do not skip)
Leave all other fields at their defaults and click OK to save the user.
Let Vergo know the user is created
Once the ODBC user has been created, fill out the Foundation Info form so the Vergo team can test the connection on our end before you proceed to the next steps.
Step 2: raise a support ticket with your IT team
Your IT team needs to whitelist Vergo's IP addresses and grant the Vergo ODBC user access to the necessary Foundation database tables. Send your IT team the following message:
"We would like to whitelist the following IP addresses for our Vergo integration:
13.58.14.240
18.219.160.98
3.143.37.24
Could you also whitelist the following Foundation database and user to enable writing data to the tables and stored procedures listed below?
Database: [your Foundation database name]
User: Vergo
Tables / Stored Procedures: Pending_po_sync_header, Pending_po_sync_detail, Sp_insert_update_jobs, Pending_timecards
Thank you."
Replace [your Foundation database name] with your actual Foundation database name before sending. If you're unsure of your database name, your Vergo implementation specialist can help you locate it.
Step 3: install the ODBC Driver
The Microsoft ODBC Driver 18 for SQL Server is required for Vergo to communicate with Foundation's database.
Who needs to install it?
Foundation Cloud (Hosted) customers: must be installed on your server.
Foundation On-premise customers: only needs to be installed on one main computer.
Download the driver
Go to Microsoft's Download ODBC Driver for SQL Server page.
In the Download for Windows section, click Download Microsoft ODBC Driver 18 for SQL Server (x64).
The file
msodbcsql.msiwill download to your Downloads folder.
Install the driver
Double-click
msodbcsql.msito launch the Installation Wizard.On the Welcome screen, click Next.
On the License Agreement screen, select I accept the terms in the license agreement and click Next.
On the Feature Selection screen, select Client Components and click Next.
On the Ready to Install the Program window, click Install.
If a User Account Control (UAC) prompt appears, click Accept.
When installation completes, click Finish.
Configure the ODBC data source
After installing the driver, you need to create a System DSN so Foundation can be referenced as a data source.
Right-click the Start Menu and select Search. Type ODBC in the search box.
Open ODBC Data Sources — use the 64-bit version if you are running 64-bit Excel, or the 32-bit version if you are running 32-bit Excel. If you are unsure, check Microsoft's guidance on choosing between 64-bit and 32-bit Office.
In the ODBC Data Source Administrator window, click the System DSN tab, then click Add.
From the driver list, select ODBC Driver 18 for SQL Server and click Finish.
In the Name and Description fields, enter the name of your Foundation database. In the Server field, enter exactly:
sql.foundationsoft.com,9000. Click Next.
Select With SQL Server authentication using a login ID and password entered by the user. Enter the Vergo User ID (
Vergo) and password (provided by your onboarding manager) you created in Step 1. Click Next.
Check Change the default database and type or paste your Foundation database name into the field. Uncheck Use ANSI nulls, paddings, and warnings. Click Next.
In the Connection Encryption dropdown, select Optional. Click Finish.
On the summary screen, click Test Data Source. You should see TESTS COMPLETED SUCCESSFULLY! in the results window.
Click OK to save the new ODBC DSN.
Step 4: install the FSI Importer
The FSI Importer is Foundation's data import tool. Vergo uses it on the back end to enable auto-sync — you won't use it directly, but it must be installed and running for the integration to work.
Who needs to install it?
Foundation Cloud (Hosted) customers: must be installed on your server AND on each computer used by anyone who will be uploading data into Foundation.
Foundation On-premise customers: can be installed on up to 3 computers. Install it on each computer used by anyone who will be uploading data into Foundation.
Download and install the FSI Importer
Log in to the Foundation Client Portal.
Navigate to:
Foundation Cloud (Hosted) customers: Resources → Downloads
Foundation On-premise customers: Resources → Software Releases
Select the download icon for the FSI Importer.
Once downloaded, open the
.exefile from your Downloads folder.Follow the installation wizard through to completion.
Repeat the installation on each additional computer that requires it (see "Who needs to install it?" above).
What happens next?
Once all four steps are complete, notify your Vergo implementation specialist. They will verify the end-to-end connection — from Vergo through ODBC into Foundation — and confirm that auto-sync is working correctly before you begin processing live transactions.
If you run into any issues during setup, contact Vergo support with a description of where you got stuck and any error messages you're seeing. Screenshots are especially helpful for ODBC configuration errors.

















