Access: FOG City Regulators
Overview
SwiftComply FOG lets you bulk-load records into your database using CSV files — saving you from entering data one record at a time. This article explains what you can import, how the process works, and the safeguards we recommend before you upload anything. Because bulk imports cannot be undone, your Customer Success Manager (CSM) is your partner on every import to make sure your data lands exactly the way you expect.
Before you begin
Reach out to your CSM to request the correct import template for your record type. Templates are kept up to date and tailored to your account's custom properties — using an outdated or generic template is the most common cause of import errors.
Make sure you have admin or import permissions on your SwiftComply account.
All import files must be saved as .csv (UTF-8 encoded).
What you can import
You can bulk-import five types of records into SwiftComply FOG:
Establishments — Food Service Establishments (FSEs) regulated under your program.
GCDs — Grease Control Devices (also called grease traps or interceptors) installed at establishments.
Providers — Service Providers (haulers) who pump and service GCDs.
Contacts — People associated with establishments, such as owners, managers, or site contacts.
Pump Outs — Historical pump-out records, typically used when migrating data from a previous system.
The import tool works the same way across all five sections — once you know the flow, you know it for every record type.
⚠️ Important: Imports cannot be undone. SwiftComply does not have a "rollback" or "undo" button for bulk imports. If you import bad data, the only way to fix it is to manually correct or delete each affected record. Always validate first, and when in doubt, work with your CSM before processing.
How the import process works
Every import follows the same three-phase flow:
1. Get the right template from your CSM
Templates contain the exact column headings SwiftComply expects (for example, the establishment name column must be labeled Name, not "Establishment Name"). Required fields are marked with an asterisk (*). Your CSM will send you the version that matches your account, including any custom property columns specific to your program.
2. Validate the file
When you upload your CSV, you'll see a Type dropdown with two options:
Validate — Checks the file for errors without saving any records. SwiftComply scans every row and reports any problems back to you, line by line.
Process — Actually creates the records in your database.
We strongly recommend always running Validate first. If there are errors, you'll see exactly which rows failed and why, so you can fix them in your spreadsheet before processing.
3. Process the file
Once Validate returns a clean result, re-upload the corrected file and select Submit. Your records will be created in SwiftComply.
Where to find the importer
From the left navigation panel, go to the section you want to import into (for example, Establishments).
Click Import.
On the Record Importer screen, click Choose File to select your CSV, choose Validate or Process from the Type dropdown, and click Submit.
A few things to know about your data
Imports add new records — they don't update existing ones.
If you upload a record that already exists in SwiftComply, you'll create a duplicate. After a successful import, do not re-upload the same file.
Custom properties must already exist in your system.
If your program tracks custom fields (for example, a "Hood Size" property on Establishments), those properties must be set up in Settings > Properties before you import. The CSV column heading must match the property's Internal Name exactly — including capitalization and underscores. Your CSM-provided template will already include these for you.
Test with one record first.
Before importing a full file, try a single row to confirm everything maps the way you expect. This is the fastest way to catch problems early.
What happens next
After a successful Process run:
Your new records appear in the relevant section (Establishments, GCDs, etc.).
Records are searchable, editable, and reportable like any record entered manually.
There is no notification email — you'll see the import summary on screen.
If validation finds issues during Process, the import will stop and report errors. No partial data will be saved.
FAQ
Q: Can I undo a bulk import if something goes wrong?
A: No. SwiftComply does not support rolling back imports. This is why we recommend always running Validate first and partnering with your CSM on the file before processing.
Q: Why do I have to get templates from my CSM instead of downloading them myself?
A: Templates are tailored to your account, including any custom properties you've set up. Your CSM makes sure you get the right version so your import works on the first try.
Q: What file format does SwiftComply accept?
A: CSV files only, saved with UTF-8 encoding. Excel files (.xlsx) and other formats won't work — save them as CSV first.
Q: My import failed with an "Invalid CSV file" error. What now?
A: This usually means the file isn't UTF-8 encoded or has formatting issues. Re-save the file as CSV UTF-8 from your spreadsheet program, or send it to your CSM for help.
Q: Can I import updates to existing records?
A: No — the importer is for adding new records only. Editing existing records in bulk is not supported through this tool.
Q: Will imported data show up immediately?
A: Yes. Once Process completes successfully, records are live in your account right away.
Need help?
Double-check formatting against the template your CSM provided.
Make sure custom property column headings match the Internal Name exactly.
Still stuck? Email help@swiftcomply.com or reach out to your CSM and we'll jump in to help.