Skip to main content

Other functionnalities

Config & Fieldsets Export

Extract a complete technical map of your Procore company configuration, including fieldsets, custom fields, and technical IDs.

This feature is a powerful tool designed for Company Admins, Super-users, and Integrators. It allows you to export the entire metadata structure of your Procore instance into a single, standardized Excel workbook.

1 - Prerequisites

Because this tool accesses sensitive configuration data across the entire organization, it requires Admin permissions on the Company-level Admin tool in Procore.

2 - How to Run the Export

  1. Select your Company in the app.
  2. Click on Export fieldset details over a selection of tools.
  3. Select Tools: A list of available tools will appear.
    • Note: The list only includes tools that have specific fieldsets configured. If a tool only uses the standard Procore fieldset, it will not appear here.
    • Shortcut: All tools are selected by default. You can use Ctrl + Click or Shift + Click to refine your selection.
    • API Names: Tools are listed by their technical API names.
  4. Click to generate the Excel file.

3 - Understanding the Technical Workbook

The resulting Excel file acts as a “live snapshot” of your Procore data model:

Tab: SUMMARY

A master list of all selected fieldsets across all selected tools. This includes relevant data to filter them, such as specific Observation Categories, Inspection Types, or Correspondence Types, and direct links to the fieldset specific tabs and to Procore.

Fieldset Specific Tabs

Each fieldset has its own dedicated tab containing:

  • General Metadata: Fieldset geenral information.
  • Direct Link: A URL to jump directly to that specific Fieldset configuration page in Procore.
  • Field List: Every field (native and custom) with their properties (Visible, Required, Data type, etc.) and their Procore Technical ID for custom fields.

Tab: ENTRIES

For all Custom Fields that use dropdown lists, this tab centralizes every available option.

  • It maps the “Label” (what users see) to the “Internal ID” (what the database sees).
  • Automatic links within the Fieldset tabs will take you directly to the relevant entries in this list.

4 - Key Use Cases

  • Integration & Mapping: Use the technical IDs to build data correspondence tables for APIs or third-party integrations (BI tools, ERPs).
  • Offline Auditing: Review your configuration with stakeholders who do not have Admin rocore access.
  • Standardization: Easily spot inconsistencies in field naming or logic across different tools.
  • Collaboration: Brainstorm and validate configuration changes in a familiar Excel environment before implementing them in Procore.

[IMPORTANT]: This is a one-way export. The file is meant for auditing and mapping purposes. Any changes or cleanups identified during your review must be manually applied within the Procore Admin interface.