Skip to main content
All CollectionsFeature overviewsSalesforce Org ModelsSupported metadata
Full list of Salesforce metadata supported in Org Models
Full list of Salesforce metadata supported in Org Models

Metadata, Org Model, Metadata types

Ksawery Lisinski avatar
Written by Ksawery Lisinski
Updated over a week ago

The article below outlines what types of Salesforce metadata are supported in Org Models.


Supported Metadata

Below is the list of supported metadata. Each metadata comes with different analytics (e.g. for fields we check dependencies & field % population while for roles or profiles, we show the list of assigned active users). If you can't find the metadata you need, or you would like us to get more information about the metadata already supported, talk to us.

  • Apex Classes

  • Apex Page

  • Apex Triggers

  • Applications (Apps)

  • Approval Processes

  • Assignment Rules

  • Auto-response Rules

  • Aura Component Bundles

  • Big Objects

  • Buttons, Links & Actions

  • Compact Layouts

  • Custom Labels

  • Custom Value

  • Dashboards (in public folders and private)

  • Duplicate Rule

  • Email Alerts

  • Email Services

  • Email Templates

  • Entitlement Process

  • Escalation Rule

  • External Services

  • Field Sets

  • Fields (Custom Field)

  • Flows

  • Flow Tests

  • Global Actions

  • Lightning Pages

  • Lightning Web Components

  • List Views

  • Matching Rules

  • Objects (Custom Metadata)

  • Objects (Custom)

  • Objects (Standard)

  • Page Layouts

  • Permission Sets (and Muting Permission Sets)

  • Permission Set Groups

  • Picklist Values

  • Platform Events

  • Process Builder Workflows

  • Profiles

  • Queues

  • Record Types

  • Remote Site Setting

  • Reports (in public folders and private limited to 100,000)

  • Report Types

  • Records (configuration records for nCino and Salesforce industries)

  • Roles

  • Sharing Rules

  • Standard Value Set

  • Tabs

  • Validation Rules

  • Visualforce Components

  • Visualforce Pages

  • Workflow Field Updates

  • Workflow Rules

  • Managed packages

Unmanaged packages are also synced, but the individual components will appear under the relevant metadata type rather than as a whole package.

Did this answer your question?