Hi!

I agree it should be possible to export locations in a simple way. The only way I can think of, and the way I have been handling it, is through the API where I can list all of my locations and make a file out of the response. An issue with this if I remember correctly is that you have to make a request for the different pages if you have many locations (which is not efficient at all in my opinion) so it is not possible in one call to list all the locations. Then editing them via API is no improvement at all compared to manually editing them in the GUI.

So to summarize, yes, location management seems to be currently very limited (as far as I know) and the only way to export the info is through API calls, while bulk editing is not really possible in any simple way.

Service Desk API for Developers | Freshservice

Just had to do this myself to get a list of all locations so I could compare against used locations in assets and requesters to delete the excess, prior to creating a translation table for data being imported that has locations stored in a different naming format. 

Exporting would be great. But so would actually being able to use the tree structure when filtering assets.  It works in workflows, where you can say “belongs” but nowhere else.  I want to filter to show all assets with a location that is nested within UK, I don’t want to have to select 15 different locations.

Thank you all for sharing your feedback and experiences around location management in Freshservice. We completely understand how important it is to have a seamless way to manage, export, and normalize location data—especially when working across regions or integrating with systems like Device42.

At the moment, exporting locations directly via the UI isn’t supported, but your points have been well noted. We recommend using the Freshservice API as a workaround for now, although we acknowledge that pagination and lack of bulk update functionality can be limiting. We're actively reviewing these types of use cases to identify opportunities for improvement.

Regarding the location tree structure, you're absolutely right. While it can be used in workflows (like “belongs to”), its absence in filters for assets and reports is a valid limitation, and we've passed this along to our product team as a feature request.

We truly value this type of constructive input—it plays a big role in shaping our roadmap. Please continue to share your needs, and we’ll keep striving to improve your experience.

Warm regards,

Freshworks