When importing data to Silverbucket it is vital to keep the structure identical to the example datasheet to ensure a flawless import:

- First row contains the names of the headers - it is not necessary to edit the first row.
- Second row in your file is where your data starts to get imported
- Columns need to be in the same exact order as in the examples
- Rows after the default structure's last column are never read / handled when importing
- Never have hidden columns in your data sheets

- Projects with simple metadata

The outcome of this import can be seen in the Projects > Listing view, for example.

1) A project called 'Support Project' with the following metadata:

Project Manager = freshUser@email.com (this user wasn't yet added to Silverbucket before the import, so the user will be created with email "freshUser@email.com")
Project's customer = City of Helsinki
Project's start date = 15th of February, 2020
Project's code = 'SP'

2) A project called 'Maintenance' with the following metadata:

Project Manager = Adam Adamson (matched by the email adam@email.com)
Project end date = 30th June, 2020
Code = 'MTNC'

Row 4 will be skipped; project name is a mandatory field. Fill in the name for the project in order to import it.

Silverbucket matches rows to Silverbucket's data case-sensitively ("SilverBucket_Support" is not considered the same as "silverbucket_support").
However, matching email fields is done case-insensitively ("Support@Silverbucket.Com" is considered the same as "support@silverbucket.com" when creating a user, for example)

If the data structure was correct, you can see the outcome in Silverbucket right after the upload. You can check this by navigating to an imported Project's Dashboard, as an example the below screenshot is from the project 'Support Project':