# Migrating Continua to new Server
**URL:** https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141
**Category:** Discussion
**Created:** [January 22, 2014, 3:47am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141 "2014-01-22T03:47:17Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@chillefeld](https://www.finalbuilder.com/forums/u/chillefeld)
#### Post date: [January 22, 2014, 3:47am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/1 "2014-01-22T03:47:17Z")
Hi everyone,
we are currently in the process of setting up a new build server to replace our existing one. Is it possible to somehow migrate a Continua installation between machines or are we better off just setting it up again from scratch?
---
### Author:  [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [January 23, 2014, 12:10pm UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/2 "2014-01-23T12:10:51Z")
Hi,
We don’t have a formal migration process, but almost everything is stored in the database.
Take a back up of the database (see the wiki page for [backing up the Continua database](http://wiki.finalbuilder.com/x/mwIZ)), install Continua on the new machine, then restore the backed up database over the database created. You may also need to copy over any settings that you have changed in the Continua.Server.Service.exe.config file.
Of course any paths specified in the configurations will need to be updated to point to folders accessible on the new server.
We plan to implement backup/restore functionality in a future version of the product.
---
### Author:  [@chillefeld](https://www.finalbuilder.com/forums/u/chillefeld)
#### Post date: [January 23, 2014, 8:31am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/3 "2014-01-23T08:31:08Z")
Thanks. I will do that.
---
### Author:  [@chillefeld](https://www.finalbuilder.com/forums/u/chillefeld)
#### Post date: [January 28, 2014, 11:30am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/4 "2014-01-28T11:30:11Z")
I have successfully migrated the database to our now server and Continua runs just fine.
However when it sends out notification mails the variable BuildUrl still contains the url of the old server. How would I go about changing this?
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [January 28, 2014, 12:11pm UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/5 "2014-01-28T12:11:16Z")
Did you customize the server url in the Continua.Server.Service.exe.config file? That would be my guess.
---
### Author:  [@chillefeld](https://www.finalbuilder.com/forums/u/chillefeld)
#### Post date: [January 28, 2014, 12:42pm UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/6 "2014-01-28T12:42:42Z")
I did not specifically customize the server url and I could not find any reference to the old server name in the config file either.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [January 28, 2014, 1:19am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/7 "2014-01-28T01:19:16Z")
You can hard code the server url in the config file using :
[code] …\\[/code]
---
### Author:  [@chillefeld](https://www.finalbuilder.com/forums/u/chillefeld)
#### Post date: [January 28, 2014, 3:16am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/8 "2014-01-28T03:16:49Z")
Okay I found the error. I had to change the server property _server.hosturl_ to the new server name and now the emails are correct too.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [January 28, 2014, 9:47am UTC](https://www.finalbuilder.com/forums/t/migrating-continua-to-new-server/5141/9 "2014-01-28T09:47:02Z")
Ah yes, I had forgotten about that property. It overrides the config file setting (which overrides the auto detection). Need to get that documented.