More ideas:
* Content manage the Expect Schema from the Help Center's API so the import's scheme is always accurate and up-to-date.
* Make the importable reports part of the process instead of the user going to a different module to run a report, edit the report into an export, and then re-import.
* Improve the user experience of the Trial Run feedback to contain visuals and details so the user understands what the import will create, update, or delete. If the import displays warnings the user must clearly understand what they need to do to correct the import.

Specifically, the suggested changes to the following imports to improve self-service:

1) Person Import → Remove redundant fields, e.g. Opt out of Serraview Live

2) Team Import, Hood Import & Occupancy Import → these imports should be consolidated as one import. Currently, we may do 2-3 imports to get allocation & occupancy into the VBS.

2a) Create a team in the system if it doesn’t already exist

2b) If the hood column is included in the import, the hood should be created on the stack in the VBS

2c) If the person has a desk associated with it, block the person’s team to the workpoint

3) Workpoint Import → Strip out the data fields not required for Basics, e.g. Charge Rule, Show Availability in Locator

4) Importable Reports for the following imports which allow the end-user to mark up changes in the file for easier importing.

4a) Buildings
4b) Floors Import
4c) Person Import
4d) Team Import, Hood Import & Occupancy Import
4e) Workpoint Import (e.g. #141)