---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Export and import custom models in ERP Canvas

# Export and import custom models in ERP Canvas {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Move a custom ERP model from one instance to another by exporting and importing a remote update set.

## Before you begin

Role required: sn_erp_integration.erp_admin

Confirm that the application scope for the custom model exists on the instance to which you're importing.

The glide.attachment.extensions system property restricts the file types that can be downloaded. This property is empty by default. Check that the xml file extension has not been added to this property. For more information,
see [Restrict attachment file extensions](https://www.servicenow.com/docs/access?context=t_DisablingTheDragAndDropFeature&version=yokohama&pubname=yokohama-platform-administration&section=t_RestrictingFileExtensions&ft:locale=en-US).

## About this task

You may need to move a custom ERP model from one instance to another. For example, after creating a custom ERP model in a non-production instance, you need to move the model to production or another non-production instance.
Export the custom ERP model and all of its related files, such as entities and operations, into an XML file within a remote update set. Then, import the remote update set into another instance.  
The XML file contains:

* Operations
* Entities
* Input fields
* Output fields
{#erpc-export-and-import-custom-models__ul_h1k_4cq_qdc}  
Note the following when exporting and importing custom ERP models:

* Internal models can't be exported and imported.
* The system value isn't imported.
* One model can be exported at a time.
{#erpc-export-and-import-custom-models__ul_gcb_nhq_qdc}

## Procedure

1. Navigate to AllERP CanvasERP Canvas Home.
2. On the Models page, select the custom model to export.
3. Select Export.  
4. Specify a location for the downloaded file (by default in the Chrome and Safari browsers, this location is the Downloads folder).  
   The export process may take a few minutes depending on the size of the model.
5. Navigate to the download location and confirm that the XML file is there.  
   The file name should look similar to sys_remote_update_set_f08252b6c3da16106f44d1af050131d0.xml.
6. Open the instance to which you're importing the custom model.  
   The following sub steps use update sets. For general information, see [System update sets](https://www.servicenow.com/docs/ZQ_8X~7qlkF6pxE1QX5AvA "An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.").
   1. Navigate to AllSystem Update SetsRetrieved Update Sets.
   2. In Related Links, select Import Update Set from XML.
   3. Select Choose File, navigate to the XML file you exported, select the file, and select Open.
   4. Select Upload.  
      The file is imported and displayed in the retrieved update sets list with the State set to Loaded. If the import fails, check that the application scope for the
      custom model exists on the instance to which you're importing.

   5. Select the file.
   6. Select Preview Update Set and check for any errors, such as a collision.  
      For detailed information about previewing and resolving any issues, see [Preview a remote update set](https://www.servicenow.com/docs/c9mHUfewQARmLN5rI510EA#t_PreviewARemoteUpdateSet "Previewing compares an update set retrieved from a remote instance to updates on the local instance to detect potential problems. You must preview an update set and address all problems before you can commit the update set.").
   7. When you're finished previewing and have resolved any errors, select Close.
   8. Select Commit update set to create a local copy.  
      For detailed information about the update set commit process, see [Commit an update set](https://www.servicenow.com/docs/95flRbEOwirbmkWU708zWA "When you have previewed an update set and have resolved any issues, commit the update set. Committing an update set applies all changes to the instance and creates a local copy of the update set that contains an update record for every change.").
   9. When the local copy is created, select Close.
   {#erpc-export-and-import-custom-models__substeps_pq4_g4p_c2c}
7. Navigate to AllERP CanvasERP Canvas Home.
8. On the ERP Models page, find and open the model you imported.
9. Confirm that you are in the correct application scope.
10. Specify an ERP system.
11. Make any other necessary changes to the model.  
    For detailed information about editing and managing models, see [Managing how models read and update the ERP system](https://www.servicenow.com/docs/QgXLFIZNnf9wfUZebaVqQQ "After you create an ERP (Enterprise Resource Planning) model in ERP Canvas, you can specify how it reads and updates the ERP system using parameters.").

*[\>]: and then