Skip to main content
Contact imports require a workspace administrator, contact access, and Work. Use a CSV import to add records or fill empty fields on matching companies and people. Use saved views when the same list and filters matter more than once.

​
Import from CSV

1

Choose the record type

Open Contacts and start an import for companies or people. Keep the two record types in separate files.
2

Upload the file

Use a header row and one record per row. Remove columns and rows that you do not want to import.
3

Map the columns

Match each CSV column to a Floral field. Unmapped columns are stored as metadata under their original headers. Remove unwanted columns from the file before uploading it. Work fields are available only when Work is active and the field exists in the workspace.
4

Review before importing

Check validation messages and the proposed mapping. Correct the file or mapping before you confirm.
Keep identifiers such as CVR and email consistent. They make later review and duplicate handling easier.

​
Saved views

Apply filters, sorting, and visible columns on the Contacts page, then save the view. A saved view stores the list setup, not a separate copy of the records. Opening it later uses current data. Update a saved view when the team changes its working definition. Use a clear name such as “Customers without an owner” instead of a personal shorthand. Personal views belong to their creator. Administrators can create and manage shared views for the workspace. A shared view does not grant access to records a member cannot otherwise read.

​
File limits and matching

Each file can contain up to 2,000 records and must be no larger than 5 MB. Commas, semicolons, and tabs are supported as separators. Companies need a name. People need a name and a valid email address. A supplied Danish CVR must contain eight digits. Floral matches companies by CVR when provided, otherwise by name. People match by email. An existing match can receive values in empty fields, but importing is not a way to overwrite a record’s existing details. Review the import results and matched records before using the same file again. Unmapped data has limits of 50 metadata keys per row, 40 characters per key, and 500 characters per value. Map information to a standard or custom field when it needs a defined type. Do not use unmapped columns for long meeting notes or documents.