Showing results for 
Search instead for 
Do you mean 

Migration from ACT! 2009 (11.0) on XP to ACT! 2012 Pro on w7

New Member
Posts: 2
Country: Switzerland

Migration from ACT! 2009 (11.0) on XP to ACT! 2012 Pro on w7

Hi everyone,


our company is currently running ACT! 2009 v 11.0 on Windows XP clients, together with a Windows XP PC used as sync server. We recently got 10 new client computers with Windows 7 x64 and a new HP PC (w7-64bit) which will be used as sync server again. On all these new computers, clients and server, should be installed the newest version of ACT! 2012 Pro.


Now my task is to:

- Migrate the database on our old "Server" to our new one: XP to w7

- Migrate the database from ACT! 2009 to 2012 Pro


In the end this should all together work fine on the new client and the database should be synced to the new server.


How would you proceed? What are the steps to take and in which order?


Thank you a lot in advance!

Platinum Super Contributor
Posts: 5,275
Country: USA

Re: Migration from ACT! 2009 (11.0) on XP to ACT! 2012 Pro on w7

Hello Mochsner,

Welcome to the Sage ACT! Online Community!


I'm unsure if you were referring to adding additional workstations, or replacing the existing - but  you certainly have 2 independent projects here: 1. Move to new server; and 2. Upgrade to 2012.


One important step before beginning the upgrade or move is to have all remotes perform a final synchronization.  Then have the users refrain from making any changes.  While there is a process to move the current remotes to a new computer, this step will ensure current data in the main database in case you have to create new remotes.


It is also important to note that users with 2009 installed can't access a database updated to 2012.  So, once the server/database is upgraded, only 2012 workstations will be able to access/synchronize.


If the workstations are to replace existing computers, that will make it easier since you can go ahead and install 2012 on them (without 2009 ever being on them).  Then move the remote databases over as needed.


For the new server, one option is to install 2012 on the new server - leaving 2009 on the old server.  This will prevent having to install 2012 on the old server and any possible problems that may arise.


Once the new server and workstation have 2012 up and running, you can then 'move' the databases (main and remotes) to the new machines and update them (opening them in 2012 will prompt for update).


Here is an article with instructions for moving remote and main databases to new computers: KB Article 19817


As a test for the updating of the main database; within 2009 - create a backup (File > Backup > Database) and then restore it on the new server with 2012 (File > Restore > Database > Restore As), being sure to give it a new name different from the current name.  This restored database would just be for testing the update, it would not become your new main database.  It could be deleted through the Tools > Database Maintenance > Delete Database option.


Of course, you'll need to think about the variables in your environment and decide the best plan of attack for these projects.  Hopefully some of this will help you determine a plan.


Greg Martin