# Urls are not same after migration from nexus 2 to nexus 3 **URL:** \ **Category:** Sonatype Nexus Repository\ **Tags:** docker, nexus-repository\ **Created:** [April 4, 2023, 11:17am UTC](https://community.sonatype.com/t/urls-are-not-same-after-migration-from-nexus-2-to-nexus-3/10404 "2023-04-04T11:17:05Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![neha.shrivastava](https://avatars.discourse-cdn.com/v4/letter/n/85e7bf/32.png) [@neha.shrivastava](https://community.sonatype.com/u/neha.shrivastava)\ **Post date:** [April 4, 2023, 11:17am UTC](https://community.sonatype.com/t/urls-are-not-same-after-migration-from-nexus-2-to-nexus-3/10404/1 "2023-04-04T11:17:05Z")
I have migrated nexus 2 to nexus 3 but URLs of repos are not same. So some applications are not reachable which is linked with nexus. Please solve my issue. Thanks, in advance! ---
**Author:** ![mprescott](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/mprescott/32/178_2.png) [@mprescott](https://community.sonatype.com/u/mprescott)\ **Post date:** [April 4, 2023, 1:10pm UTC](https://community.sonatype.com/t/urls-are-not-same-after-migration-from-nexus-2-to-nexus-3/10404/2 "2023-04-04T13:10:04Z")
Neha, if you’re talking about repository URLs that clients like maven or gradle use, then [there is a capability you can enable that produces backwards compatible URLs](https://help.sonatype.com/repomanager3/installation-and-upgrades/upgrading-from-nexus-repository-manager-2/nexus-repository-3-upgrade-wizard/configuring-legacy-url-paths). Other URLs, however, are different between Nexus 2 and 3 as there’s a fundamentally different architecture under the hood - integrations that used the REST endpoints will need to be updated. ---
**Author:** ![neha.shrivastava](https://avatars.discourse-cdn.com/v4/letter/n/85e7bf/32.png) [@neha.shrivastava](https://community.sonatype.com/u/neha.shrivastava)\ **Post date:** [April 5, 2023, 6:07am UTC](https://community.sonatype.com/t/urls-are-not-same-after-migration-from-nexus-2-to-nexus-3/10404/3 "2023-04-05T06:07:14Z")
Thanks, @mprescott to answer my question. But my main problem is- Some codes are getting error due to changes in URLs’ endpoint, as I migrated nexus2 to nexus3. Is there any solution in which there is no need to change URLs manually? Example- source URL-\>Nexus2 URL-- [https://nexus2.xyz.com/content/groups/Some-repo](https://nexus2.xyz.com/content/groups/Some-repo) NExus3 URL - [https://nexus3.xyz.com/service/rest/repository/browse/Some-repo/](https://nexus3.xyz.com/service/rest/repository/browse/Some-repo/) is this not wierd to use browse in url paths? ---
**Author:** ![mprescott](https://yyz1.discourse-cdn.com/flex047/user_avatar/community.sonatype.com/mprescott/32/178_2.png) [@mprescott](https://community.sonatype.com/u/mprescott)\ **Post date:** [April 5, 2023, 1:02pm UTC](https://community.sonatype.com/t/urls-are-not-same-after-migration-from-nexus-2-to-nexus-3/10404/4 "2023-04-05T13:02:03Z")
Unfortunately, no, you’ll need to update any scripts or automation your’e using that point to these REST endpoints. > [@neha.shrivastava](#): > > is this not wierd to use browse in url paths? I see what you mean. In this case, however, “browse” isn’t a verb, it’s the name of a data structure. Since Nexus Repository v3 supports many different ecosystems, it doesn’t store the content in a typical file/folder structure. The ‘browse’ data structure is what supports directory browsing. I can see why it would seem odd, though! ---
**Author:** ![neha.shrivastava](https://avatars.discourse-cdn.com/v4/letter/n/85e7bf/32.png) [@neha.shrivastava](https://community.sonatype.com/u/neha.shrivastava)\ **Post date:** [April 6, 2023, 7:11am UTC](https://community.sonatype.com/t/urls-are-not-same-after-migration-from-nexus-2-to-nexus-3/10404/5 "2023-04-06T07:11:14Z")
Thanks @mprescott to answer my question.