Skip to main content

Features - bulk export/import

Bulk Export/Import - Project data

Comprehensive guide for managing your project portfolio data in bulk.

This guide covers the specific implementation of bulk export/import for Project Information. Unlike standard Procore tools, this feature allows Company Admins to manage the metadata of the entire project portfolio from a single Excel file.

For general concepts and the overall process, see the Bulk Export/Import - Overview.

1 - Available Fields

1.1 - Native Fields

The following project-level fields are available for export and bulk update:

Field LabelExport NameData Type
IDidid (Required for update)
Namenamestring
Numberproject_numberstring
Activeactiveboolean
Addressaddressstring
Citycitystring
Zip codezipstring
Country codecountry_codestring
State codestate_codestring
Countycountystring
Descriptiondescriptionrich_text
Faxfaxstring
Phonephonestring
Flagflaglov_entry
Start datestart_datedate
Completion datecompletion_datedate
Warranty startwarranty_start_datedate
Warranty endwarranty_end_datedate
Estimated start dateestimated_start_datedate
Estimated completion dateestimated_completion_datedate
Time zonetime_zonestring
Square feetsquare_feetdecimal
Total valuetotal_valuedecimal
Estimated valueestimated_valuedecimal
Localisationlocalelov_entry
Currencycurrency_codestring
Officeoffice_idlov_entry
Stageproject_stage_idlov_entry
Programprogram_idlov_entry
Bid typeproject_bid_type_idlov_entry
Project typeproject_type_idlov_entry
Regionproject_region_idlov_entry
Department(s)department_idslov_entries (multi-select)

1.2 - Custom Fields

All custom fields defined in your project configurable fieldset (Text, Number, Dates, and Dropdowns, etc) are automatically detected and included in the export/import process.

2 - Field-Specific Details

2.1 - Project ID (Mandatory)

The id column is the unique Procore technical identifier. To update existing projects, this column must not be modified. If the ID is missing, the tool will NOT attempt to create a new project (no project is created via this functionnality).

2.2 - Multi-select Fields (Departments)

For fields like Department(s), you can enter multiple values separated by a comma (e.g., Department A, Department B). The tool will automatically map these names to their technical IDs during import.

3 - Data Model Reference Sheets

The export file includes dedicated tabs to help you select valid values for lov_entry fields, for example:

  • office_id / project_stage_id / project_region_id: Valid values for project classification.
  • department_ids: valid departments available in your company.
  • login_informations: company user list.
  • Custom Dropdowns: every custom list configured in Procore that is part of the project fieldset gets its own reference sheet.

4 - Technical Limitations

4.1 - Permission Requirements

This tool is intended for Company Admins. Users must have Admin rights on the Company-level Admin tool to view and modify project data globally.

4.2 - API Limitations (Not available)

Certain recently added Procore fields are currently not available for bulk update via the API:

  • Sector (sector)
  • Work Scope (work_scope)
  • Delivery Method (delivery_method)

4.3 - Fieldset Alignment

The import will fail if your Excel file contains column names that are not present in your current project configurable fieldset. Always start with a fresh export.

5 - Common Use Cases

5.1 - Syncing with External Systems

Use the number or a custom field to map Procore projects with your ERP or Accounting IDs. You can export the portfolio, paste the IDs from your other system, and re-import.

5.2 - Portfolio Cleanup

Update Project Stages, Regions, or Departments for hundreds of projects at once to ensure your Company-level reporting is accurate.

5.3 - Project Directory Audit

Export all project addresses and descriptions to identify missing information or formatting inconsistencies across the company.