This article provides a comprehensive table of all the fields available in Fieldbook for importing a booking. Each field includes a description of its purpose and the required import format to help you prepare and map your data accurately.
Overview
When importing data into Fieldbook, understanding how each field works ensures a smooth and error-free process. This reference guide outlines:
Fieldbook Data Fields available
Descriptions about each data field to clarify their use.
Import formats required for each field
This guide is helpful during the mapping stage of the import process, where you align your CSV columns with Fieldbook fields.
Fieldbook Data Fields
Below is the complete list of fields available for import into Fieldbook. Booking: Reference Code and either Customer: Name or Customer: First Name are required to proceed with the import.
Fieldbook Field | Description | Import Format |
Booking: reference code | A unique code to identify the booking. | Text |
Booking: status | Current status of the booking (e.g., confirmed, pending). | During the import process, you’ll map the values from the CSV column to the corresponding booking status in Fieldbook. |
Booking: booking contact | Name of the primary contact for the booking, which we refer to as Lead Contact within the application | Text |
Booking: booking contact + use as reference code | Option to use the booking contact as the reference code. | Text |
Booking: notes | Internal notes related to the booking. | Multiple CSV fields can be mapped to Booking: Notes, and all values will be combined into a single entry in the Booking: Notes field |
Booking: Package option | The package or add-on option chosen by the customer. | During the import process, you’ll map the values from the CSV column to the corresponding package options in Fieldbook. |
Customer: name | Full name of the customer. | Text |
Customer: last name | Customer’s last name. | Text |
Customer: first name | Customer’s first name. | Text |
Customer: date of birth | Customer’s date of birth. | Date |
Customer: gender | Customer’s gender. | Text |
Customer: email | Customer’s email address. | |
Customer: phone | Customer’s phone number. | Text |
Customer: unit no/sub premise | Unit or apartment number. | Text |
Customer: street address | Customer’s street address. | Text |
Customer: city/locality | City or locality of the customer. | Text |
Customer: state/region | State or region of the customer. | Text |
Customer: country | Customer’s country. | Text |
Customer: zip/postcode | Zip or postal code of the customer. | Text |
Customer: biography | Biography or profile of the customer. | Text |
Customer: medical information | Medical details or conditions of the customer. | Text |
Customer: dietary information | Dietary requirements or preferences. | Text |
Customer: passport number | Customer’s passport number. | Text |
Customer: passport nationality | Nationality listed on the customer’s passport. | Text |
Customer: passport issue date | Date the passport was issued. | Date |
Customer: passport expiry date | Expiry date of the customer’s passport. | Date |
Customer: emergency contact name | Name of the customer’s emergency contact. | Text |
Customer: emergency contact relationship | Relationship of the emergency contact to the customer. | Text |
Customer: emergency contact phone | Phone number of the emergency contact. | Text |
Customer: emergency contact email | Email address of the emergency contact. | |
Customer: guide note | Notes specifically for guides about the passenger on a departure. | Multiple CSV fields can also be mapped to Guide Notes, with each field creating a separate note. |
Customer: supplier note | Notes specifically for suppliers about the passenger on a departure. | Multiple CSV fields can also be mapped to Guide Notes, with each field creating a separate note. |
Customer: insurance details | Details of the customer’s travel insurance. | Text |
Customer: arrival details | Details of the customer’s arrival (e.g., flight number, time). | Text |
Customer: departure details | Details of the customer’s departure (e.g., flight number, time). | Text |