Migrating from VetCare

We're in the process of evaluating OpenVPMS as a replacement for VetCare. We've downloaded and installed Version 1.4 Beta 2 without any problems, and we're currently going through the exercise of configuring the software for our particular practice. So far, so good ... The big hurdle yet to cross is migrating our data from VetCare. I've searched the website, and believe not only is it possible, but that tools exist to facilitate the conversion. There's tantalising references to a "toolkit" or even the "OpenVPMS migration tool", but I can't find any trace of them. I know that Kettle and Kettle Spoon are involved, but I can't find any more information about the process. If some kind soul could point me in the right direction to get started, we'd be externally grateful !

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Migrating from VetCare

Hi Greg,

I have moved this topic into the implementers forum.

You are correct the data migration tools are based around the open source Kettle project or PDI as it is now called.  I discussed it's use in another post ( http://www.openvpms.org/forum/batch-import-products-tabular-file). 

Essentially we created a new Kettle step which can be used to load data into the OpenVPMS database.  To install this step into Kettle you need to:

  • Download and unzip Kettle.  From version 1.4 we are compatible with version 3 of the PDI so you can download version 3.2
  • Unzip the OpenVPMSLoader.zip file found in the import/plugin folder in the openvpms 1.4 distribution.  This should be unzipped into plugins/steps folder in Kettle.

Now you can use all the Kettle input, transformation etc steps to build transforms to take one form of data and load it into OpenVPMS.

The post I mentioned above has a sample transform that takes a text data file containing product information and creates products in OpenVPMS.  This will give you an idea of how to use the OpenVPMS Loader step.

You will need to build similar transforms for customer, patient, reminder etc information.

If you need any further advice please yell.

Cheers

Tony

 

Re: Migrating from VetCare

I would appreciate some guidance in importing data from Vetcare to OpenVPMS.

This is what I have done so far....

  • I have exported some data from vetcare (MS Access Database) to CSV.
  • I've installed OpenVPMS on a Linux box.
  • I've installed PDI (Kettle) and unzipped the OpenVPMSLoader.zip into plugins/steps
  • I've figured out how to get the data I want from the Vetcare CSV file using the CSV File Input and the Select Values transform.
  • I'm able to connect to the openvpms mysql database (SQL File Output) and browse taples, etc

It's the middle bit I don't understand....

  • I'm not sure how to use the OpenVPMS Loader transform.  I can get it to list the columninfo.fieldnames (from the CSV) but don't know what to do next.  How do I get it to populate the ColumnInfo.Mapto?  Or do I have do that manually?  

Has someone else already managed to import data from vetcare?  Do you have example transforms I could use and/or can someone explain (in simple terms) how the OpenVPMS Loader transform works?

I have some experience working with mysql databases but am struggling to understand the openVPMS database structure and the role of Archetypes.

Any assistance (even just pointing me to more reading) would be much appreciated.

Cheers,

Peter.

Re: Migrating from VetCare

Hi Peter,

You will need to use the OpenVPMS Loader step rather than direct import into mysql.  To do the mapping you need to understand archetypes which actually represent logical business models that are mapped to the physical table structure in the openvpms mysql database by the OpenVPMS loader step.  

In the case of Vetcare you can actually go directly from the access database tables using the PDI Table Input step and an ODBC connection.  Setup the ODBC connection under Windows and then create a new connection that in the Input step with a Connection Type of MS Access. Method of Access ODBC and Database name as the ODBC name you created using the ODBC administrator. 

I have a complete set of transforms for migrating Vetcare to OpenVPMS which I developed as part of my suite of tools for implementing OpenVPMS for practices.  It typically takes some time to master the mapping process but once you have done one set others are much simpler.  Even so each set of transforms for a specific legacy practice management system may take a week or more to develop.  Often there is a lot of clean work to do and also you would be surprised how badly designed some databases are.  This is unfortunately a legacy of developers having tools like MS Access which allow any one to create tables without any knowledge of third normal design techniques.  This is especially true of the Vetcare database.

In order to help you along I have attached a few of the transforms I use for Vetcare.  These migrate customer information.  Hopefully this will help flatten out the steep learning curve.

Cheers

Tony

AttachmentSize
customer - account type.ktr 3.75 KB
customer - information.ktr 8.76 KB
customer - addresses.ktr 7.84 KB
Syndicate content