You may have turned to QuickBase to help you track a process that's well under way. In that case, you've probably already entered a lot of data in another application and don't want to lose it.
Not only can you get this data into QuickBase, you can put it to work by using it to help you create a new application. QuickBase is smart enough to look at your data and create an application based on its format. In other words, you can import data and create an application with it at the same time.
If your data is in Microsoft Excel 2007 or later, you can import an .xlsx file directly into QuickBase. If your data is in a different application, you'll need to convert your data into the form of a .tsv or .csv file before importing it.
To learn how to import data from a Microsoft Project file, see Importing Project Data into QuickBase.
Check and fix the formatting of your source file.
The data you're importing must be in a format that's compatible with traditional database tables. Some spreadsheet programs like Microsoft Excel allow data anarchy that QuickBase won't tolerate. Read how to format your data for an easy import.
If your data is in Microsoft Excel, you can import the .xlsx file. Otherwise, open the file in the original program that created it, and export the file as a tab-delimited (.tsv) or comma-delimited (.csv) file. (If there's no Export command, try Save As and specify either file type.)
Tip: If you only want to import a portion of your file, you can use a simple copy and paste approach instead. Read more.
Sign in to QuickBase, and access the Add a New QuickBase Application page.
Select From File and click Next.
Click Browse to display the Choose file dialog box.
Select the file that you want to import, click Open, and then click Next.
QuickBase analyzes your data, and then displays the results.
Import Analysis Results - You can change field types or exclude a column from import. Read on to learn how.
Check the results to ensure that the field types and labels for each field (column) are correct and that the data is properly aligned. To do so:
Check the results to ensure that the Field Labels - Row 1 row contains field names. If not, turn off the First Row is List of Field Names checkbox. If a label box is blank or incorrect, type a new name in the Field Label box.
If a field type isn't correct, select the appropriate field type from the dropdown at the top of the column.
Tip: If you're importing values that are also people who'll use your QuickBase application, import those values into a User type field. (Read more about user fields.) When you're importing into User fields, you can import text or—if you've got them—email addresses. When you import text into a User field, QuickBase creates placeholders that you can later convert to user values. If you import email addresses, QuickBase immediately matches a value with the QuickBase user who's registered with that email address or creates a new user automatically. So, if you can, try importing email addresses instead of user names. You'll save time later.
Address data is a little different. If you have address data in your import, you'll assign it to subfields within an Address field.
Make sure each of your address fields corresponds to field that starts with Address:[subfield].
If the data isn't properly aligned (for instance, information shows up in the wrong fields), you must return to the source program and fix the problem there. Then try importing the data again.
When you're done checking results, click Create.
Tell QuickBase what you want to call your application and the records in it.
Within the Application Name box, type in a title for you application. Then within the Items in this application are called box, type in the term that best describes the records in your table. If you do, QuickBase uses this term instead of the more general word "record." For example, if you're managing staff assignments you might type in tasks.
When you're done, click OK.
QuickBase displays your new app's Home page.
Return to top
© 1999-2014 Intuit Inc. All rights reserved. Legal Notices.