SQL database exports give your organization direct access to raw ETO data stored in a Microsoft SQL Server (.BAK) format. They are designed for advanced users who want to run external analytics, build custom reports, or store data snapshots outside the ETO platform.
What Is a Database Export?
A database export is a downloadable file containing a full backup of your live production ETO Microsoft SQL Server database. The backup file is delivered in .BAK format, which is proprietary to Microsoft SQL Server.
Any data that exists in your production database at the time of export is automatically included; partial exports are not available.
To access your data, you'll need Microsoft SQL Server Management Studio (SSMS) and a running SQL Server instance. Once you download and extract the backup from the AWS S3 bucket, you can restore it using SSMS and query the restored database directly.
β
Exports cannot be restored in MySQL or any other database platform.
For more information on performing a restore, please review Microsoft SQL's official documentation on restoring a database backup.
Types of SQL Exports
ETO offers two types of SQL exports:
One-time export: A full backup file of your database. Attachments can be included with one-time exports for an additional purchase.
Recurring export:
Full backups are sent weekly (Fridays) and monthly (end of month).
Differential (delta) backups are generated daily to capture changes since the last full backup.
Important notes:
Exports cannot be customized (e.g. attached files cannot be added to recurring exports).
It is not possible to specify a file naming convention.
Previous backups are overwritten each cycle.
How Long Does It Take to Receive the Export?
The initial setup of the export and AWS S3 connection takes about two weeks. This setup time can vary depending on your database size and data volume.
You cannot request a specific export time. Full backups are typically delivered by the start of business hours on Fridays and at the end of each month.
How Are Exports Delivered?
Backup files are compressed, password-protected, and uploaded to an Amazon AWS S3 bucket.
When an export is complete, you'll receive a Word document containing the information needed to connect to your AWS S3 bucket, including:
AWS connection settings for your SFTP client
AWS Access Key ID
Keeper links for:
AWS Secret Access Key
Zip file password
Both export types are hosted on Bonterra-managed AWS S3 buckets. Your organization may automate the process of downloading the files from Bonterra's servers and uploading them to your own environment.
Important:
One-time exports are only available for 30 days after completion. After 30 days, the export is automatically deleted.
Connect to your AWS S3 bucket as soon as possible to confirm access before the files are deleted.
Is There a Cost?
Yes. Both one-time and recurring exports are paid offerings. To request or modify export services, contact the Account Management team here.
If you need a CSV export or partial dataset instead, this can be scoped and delivered by the Professional Services team.
How Do I Access the Data?
You can use any AWS S3 file downloader application, though we recommend using CyberDuck, a free, open-source S3/FTP/SFTP solution.
Note: If CyberDuck requests a registration key, skip this step. You can still use the program without it. If you cannot locate your backup, go to Menu β Bookmark β History β Find AmazonS3 in CyberDuck.
After downloading the zipped file, unzip the export (you'll be prompted for the password provided via Keeper).
Notes:
If you encounter errors unzipping on macOS, use The Unarchiver, a free file archiving tool. For Windows, we recommend 7zip software which can be downloaded here.
If you receive a password error when trying to unzip your export, check for a blank space at the beginning or end of the pasted password. Remove them, and try again.
Keeper Links
The Keeper links in the Word file are only accessible once and expire after one week. Open and copy the AWS Secret Access Key and zip password immediately to a secure location.
If a Keeper link expires:
Bonterra can recover the zip password for a recurring export.
One-time export passwords cannot be recovered and may require reprocessing.
Clicking on a Keeper link will take you to a page similar to the following image:
A description of the record being shared is found at the top. Clicking the eye icon to the right will reveal the hidden record.
One-Time Exports
The file name in your S3 bucket will be your ETO database name (e.g., etoclient123_ticketnumber.zip). This zipped file will contain:
Your database file (e.g., database.bak)
A folder with your attachments and imported files (if purchased).
Attachments retain their original formats and file names. Each file name includes:
AttachmentID
ClientGUID
Participant full name
TouchPointID
FormResponseID
Recurring Exports
The file name in your S3 bucket will be 'database.bak'.
What Support Can Bonterra Provide?
Bonterra can:
Provide SFTP credentials to access the AWS S3 bucket.
Troubleshoot credential or connection issues.
Bonterra cannot:
Download your files for you.
Extract data from the .BAK file.
Assist with SQL Server setup or database restoration.
Any automation or analysis involving your export data should be managed internally by your IT or data team.
Common Questions
Q: I get an error that I don't have permission to access the AWS S3 bucket.
Make sure your connection path includes your assigned folder name (e.g., 'SAASOPS-ticketnumber). Users can only access their specific directory.
Q: My one-time export is very large and won't download.
This may be due to internet interruptions. Bonterra can reprocess the export and split it into smaller zip files if needed.
Q: I get an error when restoring the export due to a missing table.
If a referenced table is missing, "comment out" that section of the restore file. For additional support, consult with the Professional Services team here.
Q: Is there a mapping document or data dictionary?
Yes. You can request a Data Dictionary/Entity Relationship Diagram (ERD) through your Account Manager or a Professional Services team member.
The ETO Data Dictionary and ERD outline many of the major database tables and relationships, though not all tables are included. An NDA must be signed before these materials can be shared.
After reviewing the documents, direct questions about specific data points to the ETO Support Team at eto@bonterratech.com. Support cannot provide SQL guidance or explain table relationships beyond the information included in the ERD.