Grandfathered and exempted tables

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Grandfathered and exempted tables

    Grandfathered and exempted tables in ServiceNow instances are treated differently from standard custom tables due to legacy entitlements and contractual agreements. Understanding these distinctions helps you manage custom table entitlements effectively within your organization’s ServiceNow environment.

    Show full answer Show less

    Grandfathered tables

    • Grandfathered tables preserve your organization’s previous custom table entitlements during license migrations, ensuring they do not count against new custom table entitlements.
    • This is a one-time process that maintains legacy custom tables in your instance without affecting new subscription limits.
    • Grandfathered tables cannot be transferred, reused, or reclassified as other custom table types.
    • If a grandfathered table is deleted, it cannot be replaced by assigning another table as grandfathered.
    • Grandfathered tables remain listed in the Custom Table Inventory even if deleted from the instance.
    • To view grandfathered tables, filter the list at uacustomtableinventory.list with the condition [Allotment type] [is] [Grandfather].
    • If you have both grandfathered and regular custom tables in an application, grandfathered tables must be mapped to a grandfathered subscription, and other tables to their respective subscriptions.
    • For mapping help, contact Customer Service and Support.
    • Once a table is assigned to a grandfathered subscription, this assignment is permanent and cannot be undone.

    Example scenario with grandfathered tables

    Your organization purchases multiple subscriptions totaling 55 new custom table entitlements. To retain 25 legacy custom tables, a grandfathered subscription with 25 entitlements is allotted. Admins must map these 25 tables to the grandfathered subscription, resulting in a total entitlement of 80 custom tables (25 grandfathered + 55 new). This ensures continuity of legacy entitlements while enabling expansion.

    Exempted tables

    • Exempted tables do not count toward your custom table subscription entitlements.
    • They primarily include custom extensions of certain system-related tables (e.g., sysportalpage, sysuserpreference) used for operational improvements.
    • To view exempted tables, use the list at uaexemptedtableinventory.list.
    • The Custom Table Guide legal schedule defines which tables are exempt, with enforcement depending on contract execution dates.

    Grandfathered and exempted custom tables are treated differently than other custom tables on your instance. Refer to your organization’s ServiceNow® contract for additional information.

    Grandfathered tables

    Depending on your organization’s legacy subscription entitlements and contractual migration, grandfathered tables might be allotted to your production instance. Grandfathered table entitlements enable preservation of your organization's previous custom table entitlements through license migration. This one-time process ensures that custom tables that currently exist in a production instance don't count against your new custom table entitlements.

    Grandfathered custom tables can't be transferred, reused, or otherwise classified as another custom table type. If you delete a grandfathered custom table, you can't classify any other custom table as a grandfathered custom table to take its place. Once a custom table has been associated with a grandfathered table subscription, it remains in the Custom Table Inventory even if the table is deleted from the instance.

    To view your grandfathered tables, enter ua_custom_table_inventory.list in the filter navigator, and then add a filter with the condition [Allotment type] [is] [Grandfather].

    If you have a combination of custom tables and grandfathered tables in one application, the grandfathered tables must be mapped to a grandfathered table subscription and the remaining custom tables to one other subscription. Reach out to Customer Service and Support for help mapping a grandfathered table to a grandfather table subscription.

    Grandfathered tables on an instance

    Scenario: Your organization purchases three new subscriptions with entitlements for a total of 55 App Engine Starter custom tables (formerly Bundled Custom Tables). To ensure your organization doesn't lose the previous custom table entitlements, a grandfather subscription with an entitlement for 25 grandfathered tables is allotted to your instance. This subscription requires the admin to identify and map the existing 25 tables. These subscriptions result in a total custom table entitlement of 80. Once a custom table has been assigned to the grandfather subscription there is no option to revert this.

    Table 1. Multiple subscriptions with grandfathered and custom table entitlements
    Subscription Number of custom table entitlements Number of mappable tables
    Grandfathered subscription 25 25
    New Subscription 1 25 25
    New Subscription 2 25 25
    New Subscription 3 5 5

    Exempted tables

    Exempted tables are custom tables that do not count towards your subscription entitlements. These tables consist mostly of custom extensions of certain system-related tables, such as sys_portal_page and sys_user_preference, that you extend for operational improvements in your production instance.

    To view a list of exempted tables, enter ua_exempted_table_inventory.list in the filter navigator.

    The Custom Table Guide legal schedule provides the complete definition of which tables are considered exempt.
    Note:
    Legal schedules are enforced based on when the contract is executed.
    To find past versions of the Custom Table Guide, see the Legal Schedules Custom Table Guide.