---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Lightweight Service Model

# Service Mapping Lightweight Service Model {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The Lightweight Service Model is an optimized architecture for storing and determining service topology. It maintains current service data without storing historical snapshots, reducing storage overhead and improving
performance for large configuration item inventories.

## What is the Lightweight Service Model {#sm-lightweight-service-model__what-is}

The Lightweight Service Model is an alternative architecture for Dynamic service instances and Tag-Based application services in Service Mapping. Unlike the traditional model, which maintains a complete history of service topology snapshots, the Lightweight Service Model stores only the current state of service topology.
{#sm-lightweight-service-model__table_ry1_pz5_gkc__entry__2}

| Traditional model | Lightweight Service Model |
|-|-|
| Stores complete history of service topology snapshots | Stores only current service topology data |
| Historical records are available for all past updates | No historical snapshots retained; timeline shows change points but not full history |
| Slower update cycles due to historical data management | Faster update cycles |
| Can query past service topology states and change history | Can query current state only, with direct access to service topology data |
[Table 1. Comparison of traditional and Lightweight Service Model]

{#sm-lightweight-service-model__table_ry1_pz5_gkc}

## Benefits of the Lightweight Service Model {#sm-lightweight-service-model__what-to-expect}

Service Mapping AI capabilities enable creating services at scale. While scaling up the mapping, the Lightweight Service Model becomes crucial for scaling up the performance.

When a service operates under the Lightweight Service Model, service topology updates are significantly faster because the system doesn't maintain historical snapshot data. In addition, storage requirements are reduced because only
current service topology data is stored.

## Converting a service to Lightweight Service Model {#sm-lightweight-service-model__important-notes}

Conversion to the Lightweight Service Model is permanent and one-way. Once you convert a service to Lightweight Service Model, this change can't be reversed. Historical snapshots that were stored under the traditional model will be
deleted and can't be restored.

When you convert a service to Lightweight, the system optimizes how it stores and manages data across the service hierarchy tables. The service types that can be converted to Lightweight are Tag-Based and Dynamic.  
Figure 1. Lightweight Service Model related link Use the Lightweight Service Model related link to convert a service. For the full procedure, see [Convert a service instance to Lightweight Service Model](https://www.servicenow.com/docs/SQdfV67NQXreLi~KdtkNRQ "Convert a Service Mapping service instance to Lightweight to minimize storage footprint and optimize performance.").
**Related tasks**   

* [Convert a service instance to Lightweight Service Model](https://www.servicenow.com/docs/SQdfV67NQXreLi~KdtkNRQ "Convert a Service Mapping service instance to Lightweight to minimize storage footprint and optimize performance.")