Importing Prior CMD Data
|
<< Click to Display Table of Contents >> Navigation: »No topics above this level« Importing Prior CMD Data |
CMD 2017 can import data from CMD 2012-2016. Data from prior versions will have to be imported by Software for Ministry at a cost of $35. If you update to CMD 2017 and have a version of CMD prior to CMD 2012, you'll need to contact us for details.
Important Note: You should do the data import only on the machine that actually hosts CMD 2012-2016's data, and that will serve as the host for CMD 2017's data.
Before using the import function, please back up a safety copy of your CMD data in your current version before you start the import in CMD 2017!
To import data from CMD 2012, click Utilities | Import Prior CMD Data | Import 2012 Data.
To import data from CMD 2013, click Utilities | Import Prior CMD Data | Import 2013 Data.
To import data from CMD 2014, click Utilities | Import Prior CMD Data | Import 2014 Data.
To import data from CMD 2015, click Utilities | Import Prior CMD Data | Import 2015 Data.
To import data from CMD 2016, click Utilities | Import Prior CMD Data | Import 2016 Data.
Note that you cannot simply backup and then restore data from CMD 2012-2016 into CMD 2017.
If you attempt an import but experience any difficulty, don't panic! Just contact us and we'll help you get it done.
When the Import 2012 Data dialog appears, click the Browse button to find the path to the CMD 2012 data. If you setup CMD on a single computer and have only one data file, chances are the data file will be located in a folder one level under the c:\cmd2012\cmd2012config folder. If the data's in a different place, click the Browse button to find the folder that contains the CMD 2012 data file you wish to import.
Once you are satisfied that you have the correct data folder, click the Import Data button to begin the process. CMD 2015 will be importing information from nearly 4 dozen data tables, so it may take a few minutes. However, most files will be imported in a matter of a few seconds.
The e-mail address in case of problems is: mic@softwareforministry.com
CMD 2017 will copy the contents of your current CMD Pictures folder and place it under the new CMD folder structure we started with 2013. The path for the data in CMD 2017 is C:\CMD-SFM\WebApps\CMD Pictures. It is placed there because that's the only way the pictures would be visible to the phone or web apps in CMD.
To actually import the pictures into CMD 2017, click the Browse button to first locate the folder that currently holds the pictures that CMD uses. Once you have located it and selected it, click the Import Pictures button after the Browse dialog has closed and the pictures will be imported. Note that the pictures are still in their original folder. Once you are satisfied that CMD 2017 is working correctly for you, you are free to delete the old pictures folder to recover some space on your hard drive.
Importing from 2013-2016 is similar to importing from CMD 2012 except that you don't have to worry about importing pictures. If you have been using CMD 2013-2016 with pictures prior to importing, they are already in place and available for your 2017 data.
You will, however, need to find the CMD 2013-2016 data files you wish to import. To find them, click the Browse button. They will be located in the C:\CMD-SFM\Data folder. Under this folder, there will be a specific folder for the data for specific years: C:\CMD-SFM\Data\Data 2013, etc. Click onto the folder of the data file you wish to import, and then click OK. That will bring you back to the Import dialog. Click the Import Data button to begin the actual import process.
Software for Ministry offers limited data import from other programs on a contract basis. Generally the fees are quite small, and the user must supply Software for Ministry data in a format that we can use. Contact us directly for pricing and format information if you wish to import your data from another program.