Use asset import and export to move reusable assets in Leapwork Performance between projects or environments.
Before you begin
-
Ensure you can access the asset you want to export.
-
Ensure you can create assets in the target project or folder.
-
Use Leapwork Performance asset packages in
.zipformat.
Raw .jmx and .har files use a different import flow. See Import JMX and HAR assets.
Export an asset package
-
Open the Explorer in Leapwork Performance.
-
Right-click the asset you want to export.
-
Select Export.
-
Save the downloaded
.zipfile.
Import an asset package
-
Open the Explorer in Leapwork Performance.
-
Select the target project or folder.
-
Right-click the location.
-
Select Import.
-
Select the
.zipasset package. -
Wait for the import to complete.
-
Open the imported asset.
Verify results
-
The asset appears in the selected project or folder.
-
The asset opens without errors.
-
Dependent assets are available.
How asset packages behave
-
Export includes the selected asset and its dependencies.
-
Import creates new copies in the target location.
-
Import does not overwrite existing assets.
-
If a name already exists, Leapwork Performance adds a suffix such as
(1). -
Imported assets are created in the selected location.
-
This flow does not export run results.
Troubleshooting
Why does the import fail immediately?
You may have selected a .zip file that is not a Leapwork Performance asset package.
Use a valid exported asset package.
Why does the import fail with a package error?
The package may be empty, corrupt, or invalid.
Export the asset again and retry the import.
Why can I not find the imported asset?
The asset may have been imported into a different location.
Check which project or folder you selected before starting the import.
Why was my existing asset not replaced?
Import does not overwrite existing assets.
Leapwork Performance creates a new copy with an adjusted name.
Why can I not import my JMX or HAR file?
This flow only supports .zip asset packages.
Use Import JMX as Sequence or Import HAR as Sequence for those file types.
How do I confirm the issue is resolved?
-
The asset appears in the expected location.
-
The asset opens and behaves as expected.
What should I do if the issue persists?
-
Verify the package type and source.
-
Export the asset again.
-
Repeat the import process.