When moving over to IrisBG, data migration of your existing data is usually required. The work involved will vary depending on your data platform, the complexity of your data and the data quality. We are confident that we can carry out a successful data migration project from any readable data source.

We have experience migrating data from a wide range of data sources, such as:

  • Collection management software (BG-Base, Atlantis Botanic Garden, BG recorder, Demeter, Brahms, KE Emu, etc).
  • Desktop database platforms (Paradox, dBase, Microsoft Access, FileMaker Pro, etc).
  • Relational databases (Microsoft SQL Server, SQLite, MySQL, etc).
  • GIS and CAD systems (Esri ArcGIS, Autocad, etc).
  • Multi value databases (Advanced Revelation, OpenInsight, etc).
  • Spread Sheets and Documents.

The migration process

Data migration is carried out as a two stage process. After having received the data, we will first convert it to an accessible format and structure. The next phase is to map all the data to the relevant parts of our system. Usually, most of the migration is straightforward, but some aspects can be more difficult. In certain cases, we may locate usage that is not directly supported in IrisBG, in which case either support will be added for this type of data, or it is decided in collaboration with the customer on how to move this data over. Most importantly, we ensure that all relevant data is moved over.

How long does the data migration take?

To minimize disruption, we always try to complete the project in as short as time as possible. When planning the project, we will analyse a copy of your data and also ensure that we have sufficient resources available during the project.

A data migration project would normally start on a Friday afternoon with you sending us your latest data. The project will be completed within 9 days with a delivery no later than Monday, giving a maximum downtime of 5 working days. It is important that you are available for questions during the project, especially at the end of the week.

During this time, you can use the old system, but no data should be added or changed.

Improving data quality

Data migration is supervised by a software engineer with a degree in botany. In addition to moving the data over, we also carry out data laundry if necessary, such as removing duplicate taxa, cross checking name spelling, etc. We also offer the option to supply relevant APG III classification above genus and to map your existing genera to family according to APG III.

We are confident that we can provide a very high level of service and ensure that all the data integrity is kept intact and most importantly, that the knowledge recorded over time is transmitted as transparently as possible. As part of this service, we also supply the customer with a data migration report when the project is completed.

Data Migration Testing and Approval

Although a huge amount of effort has gone into ensuring that we deliver a high quality data migration service, we cannot guarantee that the data migration is performed with 100% accuracy. In most cases, our data migration projects are delivered without any issues. However, if we need to resolve any issues where data is missing or been transferred incorrectly, we will either send an updated database or send you prepared database update scripts. If issues are discovered early (first pass), before users start changing and adding data, we are in a much better position to correct the data.

Testing and Approval (If issues are discovered, please report back to the IrisBG team as soon as possible).

  • First Pass Approval (1-3 days): The data migration has been checked and the overall impression is positive (All the data appears to be transferred correctly). A selection of records that represents the variation in the colllection data have been compared with the original records and several reports and statistics have been analysed (see suggestions below). At this junction, you can start to enter and change records and it is considered very unlikely that major adjustments to the data migration are necessary.
    • Select 10 different Accession and Taxa that represent the variation in your collection and compare these with old and new database. The test should include related data such as images, references, map coordinates, common names, etc.
    • Select 2 or 3 areas in the garden that you will check in more details through reports and mapping.
    • Run a number of comprehensive reports and spend some time going through the results to ensure that the details are correct. Run the reports for the whole collection and for selected locations. Recommended reports are :
      • 01/Obj01-Accession catalogue
      • 02/Item02-Items Data
      • 03/Tax01-Taxa
      • 05/Stat03-Collection Overview
      • 06/Stat05-Complete record count
    • Open the different maps and explore the collecion data.
  • Second Pass Approval (1-2 weeks): The data migration has been checked in more detail over a 1-2 week period whilst using the system.
  • If any issues are discovered at a later date, we will do our best to resolve the problem.

What do we charge?

Each individual project can vary considerably, both in complexity and data quality and it is for that reason, that we price each project individually. After having received a copy of your data, we will be able to provide you with a fixed price for this service.

Can I use the Data Import Module?

Can I use the Data Import Module to populate my new database?

This depends on the complexity and quality of your dataset. More details about the difference between our Data Migration Service and the Data Import Module can be found our the Data Import Module page.

Last Updated 07 Mar 2017
Botanical Software Ltd © 2017   |   Privacy Policy