Confluence migration to a new server with new DNS
Asked by Eddy Fras:

Hi,

I have to migrate an existing couple of Confluence/Jira servers to new VMs that will be both accessed with new DNS entries.

Each Confluence space is linked to a Jira project (Confluence and Jira are linked with an AppLink) and a shortcut to the project has been automatically added in the left menu in the corresponding Confluence space.

I read this discussion talking about changing URLs in pages : [https://community.atlassian.com/t5/Confluence-questions/Change-URL-s-in-database/qaq-p/247617](https://community.atlassian.com/t5/Confluence-questions/Change-URL-s-in-database/qaq-p/247617?)

But even when I updated the different tables in DB and created the appropriate AppLink, the shortcut to the Jira project is not updated, still pointing to the old Jira URL.

How can we change that ?

Thanks !


Answers:
author: Stephen Sifers
body: Hello Eddy,

From what you have described you have a solid understanding on migrating the Confluence and Jira instances to a new server. The issue you are mainly facing will be the FQDN and DNS change.

Ensure you are following the best practices for changing your Base URL. Best practices can be found here: [Configuring the Server Base URL (Confluence)](https://confluence.atlassian.com/doc/configuring-the-server-base-url-148592.html) , [Configuring the Base URL (Jira)](https://confluence.atlassian.com/adminjiraserver/configuring-the-base-url-938847830.html)

When you do change the Base URL you will have to do the following ([Source Document](https://confluence.atlassian.com/kb/how-to-update-the-url-for-an-application-link-338364279.html)):

* You can remove and re-create all of them; Or
* You can edit them through the database.

      SELECT PS.id, PS.propertyvalue, PE.propertytype, PE.property_key FROM propertystring AS PSINNER JOIN propertyentry AS PE

I have had the best experience with removing and re-adding the application links. As always when doing this, always ensure you test on test instance using your developer license when possible. If you are new to using the developer license see: [How to get a Confluence Developer license](https://confluence.atlassian.com/confkb/how-to-get-a-confluence-developer-license-152044449.html) AND [How to get a JIRA Developer License](https://confluence.atlassian.com/jirakb/how-to-get-a-jira-developer-license-744526918.html).

You may run into issues if you have URL links and not application links. URL pasted links or hardcoded links will NOT be updated when you correct your application links. A work around for this would be to remove your A record of your old DNS entries and add CNAME records pointing from your old servers to your new servers. Do this after you have completed the migration.

I hope you find this helpful, let us know if you need further assistance.

-Stephen Sifers

comments: author: Eddy Fras
body: Hi Stephen,

Thanks for your reply.

Actually, I got an answer to my question through support channel and a bug has been opened for this : <https://jira.atlassian.com/browse/CONFSERVER-57361> .

The workaround proposed by support is ok, I just had to add double quotes for my Postgresql client :

```
UPDATE "AO_187CCC_SIDEBAR_LINK" SET "HARDCODED_URL" = REPLACE("HARDCODED_URL",'<OLD_BASE_URL>','<NEW_BASE_URL>');
```

Regards,

Eddy


author: Stephen Sifers
body: Very happy to know you were able to get it working. And thank you for posting your confirmed work around!

-Stephen Sifers


Tags: confluence-server

server