The Freshservice IT Asset Management (ITAM) architecture improves upon ITAM Classic by providing unified service operations, infrastructure visibility, and automated dependency context. This documentation details structural architecture changes, feature availability updates, and database mapping logic to help you migrate your workspace successfully. 

TABLE OF CONTENTS

• Evaluate the operational shift from ITAM Classic
• New Freshservice ITAM architecture
  • Automated Asset Discovery and access
  • Data Centralization and Operational Intelligence
  • Application Dependency Mapping (ADM) 
• Post-upgrade changes

Evaluate the operational shift from ITAM Classic

The Freshservice ITAM alters how your organization tracks configurations by transitioning the asset lifecycle from a passive database into an active infrastructure intelligence layer.

• ITAM Classic framework: Focused primarily on standalone asset inventories, traditional hardware lifecycles, and cost compliance. It functioned as a static asset registry that documented ownership, location, and user assignments without contextual visibility into surrounding business applications.

• The Freshservice ITAM framework: Delivers deep ecosystem awareness by embedding automated hybrid discovery directly into daily service workflows. It actively updates the Configuration Management Database (CMDB), transforming it from a manually maintained database into a live, trusted system of record. This automation powers smarter ITSM and ITOM decision-making by evaluating risks before adjustments are deployed.

Freshservice ITAM architecture

The updated architecture introduces advanced modules that expand your visibility beyond standard hardware lifecycle tracking. The key capabilities include:

Automated Asset Discovery and access

Asset management identifies network-connected devices and secures the credentials required to scan them. Use these features to maintain an accurate inventory across cloud and on-premises environments.

• Scan and discover: Automates the detection of devices across diverse cloud and on-premise environments. It uses Active Directory integration and customizable scanning schedules to ensure the inventory remains current without manual intervention.
  
  

• Secret vault: Acts as a hardened repository for the keys, roles, and credentials required for deep-system scans. This ensures that discovery agents have the necessary permissions to retrieve configuration data without compromising sensitive access logs.

Data Centralization and Operational Intelligence

You can manage lifecycles and evaluate the impact of assets on business operations. It helps you to  link hardware and software to specific services to ensure contract compliance and reduce financial risk.

• Configuration Management Database (CMDB): Serves as the single source of truth for all Configuration Items (CIs). By linking assets to specific business services and tracking licenses or contracts, it minimizes financial risk and simplifies audit readiness through dependency mapping.
  
  

Application Dependency Mapping (ADM) 

Application Dependency Mapping (ADM) builds insightful models of IT services and applications in the context of your business services.

After configuring and running autodiscovery jobs, the dependency mapping module picks up on communication patterns, which you shape through Application Groups. Application Groups are generated using sets of rules that define the starting points for your applications, and Logic Templates define how discovery traverses the network and when it stops for each application.

Post-upgrade changes

After migration, your workspace includes:

• A continuously updated CMDB.

• Expanded discovery coverage across hybrid environments.

• Infrastructure and service dependency visibility.

• Enhanced change impact analysis.

• Compliance and lifecycle management capabilities.

• Modernized reporting and analytics tools.