Next steps when replatforming apps to ServiceNow using ERP Semantic Mining

  • Release version: Australia
  • Updated March 12, 2026
  • 3 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 Next steps when replatforming apps to ServiceNow using ERP Semantic Mining

    After identifying legacy ERP candidates with ERP Semantic Mining, ServiceNow customers can use AI Platform products to replatform these apps efficiently. Although ERP Semantic Mining will be deprecated in future releases starting with Zurich, it remains supported for existing instances. The process involves leveraging ERP data through remote and extraction tables to build modern apps on the ServiceNow AI Platform.

    Show full answer Show less

    Building New Apps with ERP Data

    ServiceNow Studio enables customers to create new apps that consume ERP data directly, eliminating extra data retrieval steps seen in legacy apps. When replatforming, apps can be designed to pull data directly from third-party sources instead of relying on ERP systems, enhancing efficiency. Consider consolidating multiple similar legacy candidates into a single comprehensive app using low-code tools to improve functionality and maintainability.

    Low-Code and Pro-Code Builders

    ServiceNow offers various app builders to quickly develop apps using custom ERP data fields, including ServiceNow Studio and templates. These tools allow integration of ERP models and remote tables with existing ServiceNow tables, facilitating seamless data combination and app creation tailored to business needs.

    Accessing ERP Data Programmatically

    Customers can query ERP data programmatically through the Glide API, providing flexibility in how ERP data is accessed and used within ServiceNow apps.

    Post-Replatforming Considerations

    Once apps are replatformed, they utilize live ERP data via Zero Copy Connector for ERP without writing back to the source system. It is important to continue accessing ERP data only through remote and extraction tables for building apps, flows, and workspaces. Legacy code that is no longer referenced can be safely removed from the ERP system, simplifying maintenance.

    After you use ERP Semantic Mining to identify legacy ERP (Enterprise Resource Planning) candidates, use additional ServiceNow AI Platform products and resources to replatform your app.

    Important:
    Starting with the Zurich release, ERP Semantic Mining is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported.

    First, identify the customization you want to replatform from the ERP system with ERP Semantic Mining.

    Then, use the remote tables and extraction tables linked in the candidate mining results for fast access to ERP data.

    That ERP data can be used as a data source when you build new apps on the ServiceNow AI Platform, for example, with ServiceNow Studio.

    Build a ServiceNow app that consumes ERP data

    The next step in replatforming with ServiceNow Studio for ERP (Enterprise Resource Planning) is to build an app on the ServiceNow AI Platform that consumes the ERP data.

    As you plan to replatform a legacy app on the ServiceNow AI Platform, consider where the data is coming from. For example, an old app may retrieve data from a third party into the system of record. When you build a new, replatformed app on the ServiceNow AI Platform, you can configure the new app to pull data directly from that third party. Using that method, the Zero Copy Connector for ERP model no longer pulls the data from the ERP system, which adds an extra step of retrieval.

    Working with similar candidates when replatforming apps

    If ERP Semantic Mining shows that a candidate has a number of similar candidates, consider building one app that meets the needs of some or all similar candidates when you replatform.

    When you replatform a custom app from the system of record, you don't have to replicate the old app exactly. Use the replatforming process to design a better app. For example, an app that addresses the needs of multiple similar candidates in a single, new app built using low-code tools on the ServiceNow AI Platform. ServiceNow Studio is the quickest app to use, but there are other builders available to you, depending on your licensing.

    ServiceNow low- and pro-code builders

    After you identify ERP data to replatform, citizen developers can use ServiceNow builders to create apps quickly from the data. Any custom fields that exist in the ERP system of record, such as SAP, can be leveraged by the apps you build using the ServiceNow AI Platform.

    Use any of the following ServiceNow builders to create apps using custom data:

    For example, use in ServiceNow Studio, use a template (or build the app from the ground up) and incorporate remote tables using ERP models and remote tables. You can combine legacy data from the ERP models and remote tables with other ServiceNow data in tables.

    Using Glide to query ERP data

    You can also access data from the system of record through the Glide API.

    For more information, see Sample Glide query for ERP data in ERP Semantic Mining.

    After you replatform custom code to a ServiceNow app

    Replatformed apps on the ServiceNow AI Platform use live data from the system of record without writing any code back to it.

    After you have identified candidates to replatform and taken the recommended action in ERP Semantic Mining, you must only use Zero Copy Connector for ERP to access the remote tables and extraction tables. These tables are data sources for building apps, flows, and workspaces.

    If you're sure that legacy code on the system of record isn't referenced elsewhere, you can remove it from the system after it's replatformed.