I think you cover most points, the only thing that comes to mind at the moment is for the user to check that the version of Moneydance they are currently using is compatible with the Operating system version on the new machine.
MD Support: This post highlights the need to have articles that cover Frequently asked questions, this is clearly one of those, but things like resetting sync comes up often enough the have an article as well.
Instead of having a single KB article that can be referred to for a FAQ what we have are frequent re-posting of instructions.
Thank you for your reply and your work on drafting the KB article.
I think that you've provided a thorough explanation of the steps required.
I do think that there should be some mention of whether or not syncing should be temporarily halted when performing the transfer. I recently transferred an installation and in my mind I felt I should halt syncing but I'm not sure that it was necessary. I think it would put at ease those folks who sync and are contemplating whether or not to halt syncing.
If I may offer a suggestion for the draft. I think that breaking the process down into individual Step numbers: Step 1, Step 2, Step 3 (as opposed to just paragraphs) would make the process a little more fool-proof.
There's a typo in the last sentence of the draft...
send a message to our support team about which version you are currently version,
The word 'version' just before the comma should be changed to 'using'.
That's about all I can think of for now.
Thanks again for getting back in touch. I look forward to seeing the final draft.
1. The need to ensure that the version you are using is compatible with the Operating system version on the new machine. MacOs seems to be particularly sensitive here. While it is mentioned I do not think it is strong enough and could be easily glossed over.
2. The method outlined requires you to reinstall any extensions you are using and to reset preferences, you may like to consider a process that removes this need.
3. I do not feel the paper covers migrations when you are in a syncing relationship. While replacing a secondary system should be a piece of cake relatively speaking seeing you do not have to copy the data set, and I think the paper needs expansion for this, replacing the master would require some planning. The method usually advised is to tear it all down and rebuild from scratch. I'm not a fan of such methods in a controlled migration. I think it should be investigated the possibility of setting up the shared drive, Dropbox folder if those methods are used as one of the first stages of the migration.
With this data in place I believe moving the data set should mean the computer can continue in the same roll without any further intervention.
Moneydance does not really have a pause function on syncing, so the approach I think to deal with that is that Moneydance should not be running on any machine during the migration, and all syncing should be completed before the migration is started..
Some time ago I wrote down what I thought could be the approach for replacing a primary system in a syncing relationship. This has NOT been tested it is merely theoretically based on what I have been able to find out about syncing.
I wrote it as I would write a general instruction document. Use as you wish.
Replacing the Primary Computer.
There are likely to be occasions when you wish to replace the primary system in a syncing relationship. For example you have purchased a new computer and wish to retire the old.
This procedure assumes you have completely functioning solution, i.e. it is not designed to replace a failed system. It also assumes you have a copy of the Moneydance installation kit for the same version as you are already using, a Moneydance syncing solution should have the same software version, including the build number, on all systems.
The intention here is to create, on the replacement system, a functioning Moneydance system that has the syncing relationship as it existed with the old system, along with existing extensions, preferences etc all intact.
As always before you commence your should take a Moneydance backup, even though we will not be altering any data on your existing system, a backup is always a wise precaution. For the purpose of describing the solution I will be assuming that your data is in the default location, you will need to make appropriate allowances if that is not the case.
Also before starting you should ensure all systems have up-to-date data and that Moneydance is not running on any system. Do not start Moneydance on any system until indicated.
Moneydance separates the program data from user data and user preferences. User level information is stored under the .moneydance folder that is located in your home directory. This is the data we are interested here. The steps given here also avoid making any assumptions, hence will be mirroring the existing set up.
1. On the replacement system create a user account with the same name as the user on the existing machine.
2. You will be using the same syncing mechanism, so if using Dropbox Folder install the dropbox client and select the same location on the replacement system as is on the existing system, if using Shared Folder attach to the shared folder using the same drive letter. Dropbox Connection requires no specific setup.
3. On the existing system ensure that Moneydance is not running, then copy all folders and data from the .moneydance folder down, I would recommend using some USB connected device as it makes this completely separate from any dropbox or shared data and thus can avoid some potential confusion.
4. Copy the data from the USB devices onto the new system under the user’s home directory. This creates the .moneydance folder structure. At this stage the Moneydance user data on the two systems should be a mirror of each other in all ways.
5. Install the Moneydance software onto the new system.
As said above Moneydance should not be running on the system you are replacing, provided this migration has worked you will not run Moneydance again on this system at least until some changes are made to it.
6. Start Moneydance on the new system.
7. At this stage it is necessary to validate Moneydance operation on the new system. The following steps are suggested.
a) Moneydance should have started by opening your existing data.
b) Check to make sure your copy is registered.
c) Check the preferences to see that they have been carried over.
d) Make sure your custom reports (if any) are present.
e) Check the transaction registers to make sure data is present and correct.
f) Check under the File → Syncing menu to ensure that it would be possible to set the data to “Don’t Sync” - this confirms the system as the master.
8. Provided the system has passed previous tests you should enter some transactions to ensure that data is replicated correctly (Do not start Moneydance on the old master system!)
9. If all tests are passed it is time to ensure the old master system cannot cause any problems. At a minimum the original data directory tree under .moneydance/documents should be deleted.