How to Implement a Custom Import in Quickbase

Quickbase supports Custom Imports by letting you import data into a table, define how fields map, choose whether to copy records or merge/update existing records, and then save the import settings so you can run the same import again later.

How to Implement a Custom Import in Quickbase

Step 1: Prepare the destination table by identifying the table that will receive the data.

• Make sure the destination fields already exist and have the right data types.
• If you plan to update existing records instead of only adding new ones, you should also identify a merge field with unique values shared by both source and destination.
• Quickbase uses the presence of the destination table’s merge field to determine whether the import behaves like an update import.

Step 2: Decide your source type. Pick the source that matches your use case:

• Another Quickbase table/app for repeatable internal imports
• CSV / Excel / pasted data for external data loads
• Pipelines if you want automation or transformations before loading data

Step 3: Open the destination table’s import screen.

In the destination app, open the target table, then go to More and choose the import option:

• Import into a table from another table for Quickbase-to-Quickbase imports
• Or the outside-data option for CSV/Excel/manual imports

Step 4: Create a new import from the import screen, choose Create a new import.

• If importing from another Quickbase app, select the source app and then the source table.
• Please note: Quickbase limits this flow to apps you can access and that are on the same billing account as the destination app.

Step 5: Choose the import type by selecting one of these main modes:

• Copy records if you want to add records into the destination table
• Merge in if you want to update existing records in the destination table based on a matching unique field

Step 6: Map source fields to destination fields

• This is the core of the “custom” setup. Match each source column/field to the correct destination field.
• For related-data imports, Quickbase can also import into lookup fields if requirements are met, such as permission to view parent records and uniqueness on the lookup field.

Step 7: Configure merge behavior carefully

• If you selected Merge in, set the unique matching field correctly.
• This is what tells Quickbase whether an incoming row should update an existing record or be treated as new.
• A bad merge-field choice is one of the most common causes of duplicate or misapplied updates.

Step 8: Test with a small sample first Before loading everything, import a small subset.

Please make sure to confirm the following:

• New records are added where expected
• Existing records update correctly
• No duplicates are created
• Dates, users, lookups, and numeric fields land correctly
  Quickbase notes several field-specific behaviors, such as importing users by email address and special handling for address/list-user style data

Step 9: Save the import settings

Once the mapping and behavior are correct, click Save & Import if you want to preserve the import definition for reuse.

• Quickbase states that saving the settings lets you repeat the same import later without reconfiguring it, which is the closest thing in the UI to a reusable “custom import.”

Step 10: Re-run the saved import as needed

The next time you need the same load, return to the same destination table and launch that saved import instead of rebuilding the mappings.

• This makes recurring data syncs much faster and more consistent. Quickbase also notes that stored import processes can be triggered again later from the UI.

Two Optional Steps to Add Advanced Customization to your Quickbase Custom Import

Optional Step 1: Add a button or report-driven shortcut

• If users need to run the import easily, Quickbase supports creating copy/import buttons and copying records from reports to another table.
• This gives you a more guided, semi-custom user workflow without needing to rebuild the import each time.

Optional Step 2: Automate with Pipelines or API

• If you need the import to run on a schedule, from cloud storage, or with transformations, use Pipelines.
• If you need programmatic control, use API_ImportFromCSV for adding/updating records or API_RunImport for running a defined table import.

Top 10 Key Benefits of Quickbase Custom Imports

1. Reusable setup
   You configure the mapping once and save it, so later imports are much faster.
2. Consistent field mapping
   Saved import settings reduce manual remapping and make repeat imports more reliable. This follows directly from Quickbase’s saved import behavior.
3. Supports both inserts and updates
   You can either copy in new records or merge into existing ones, which covers most operational import scenarios.
4. Reduces duplicate records
   Using a merge field allows Quickbase to update matched records instead of creating duplicates.
5. Works across Quickbase apps
   You can import from other Quickbase apps you have access to, which is useful for cross-team workflows.
6. Supports external data sources
   Quickbase can import from outside sources like Excel, CSV, and pasted data, not just internal tables.
7. Can link related data
   Imports can target lookup fields in the right conditions, which helps connect child records to parents during load.
8. Can be user-friendly for recurring operations
   Saved imports, report-based copy actions, and import buttons make the process easier for non-technical users.
9. Can scale into automation
   When manual saved imports are not enough, the same overall pattern can be automated through Pipelines.
10. Can be extended programmatically
    If your use case outgrows the UI, Quickbase provides import APIs for scripted or integrated implementations.

Best-Practice Checklist

• Use a truly unique merge field for update imports.
• Test on a small sample before full import.
• Use email addresses for user-type imports where possible.
• Use Pipelines when you need scheduled, transformed, or multi-step imports.
• Use API_ImportFromCSV or API_RunImport for system-to-system integration.

By: April Barragan

Email: abarragan@quandarycg.con

Date Updated: 12/09/2025