Introduction for our new customers

You’ve received this document because you’re having a conversion from custom made software, or from fellow supplier’s software which we haven’t converted before.

Introduction for fellow suppliers

You’ve received this document because your assistance has been requested, to deliver your client’s data.

For both cases, this document will describe which data to deliver and how.

Databases

The preferred method is to convert from the original database, or a copy of it. In most cases, a backup can be used for this. In the list below, you’ll find the accepted files for each database engine.

Database engine	File extention	File description
dBASE	.dbf (+.dbt and other related files)	Database files
DBISAM	.dkp	Database files
ElevateDB	.edbbkp	Database files
Firebird, Interbase	.fdb or .gdb	Database files
Microsoft Access	.mdb or .accdb or .accde	Database files
Microsoft SQL Server	.bak or .dat	Back-up file
Microsoft Visual FoxPro	.dbf (+.dbc and other related files)	Database files
MongoDB	.bson and .json, or .archive	Mongodump
MySQL	.sql	SQL script (create tables, insert etc)
Paradox	.db (+ related files)	Database files
PostgreSQL	.sql	SQL script (create tables, insert etc)

Exports to other formats

If your database engine is not listed above, it is not supported by our conversion tooling and software. In this case, you’re requested to deliver according to one of these options:

• Converted to a different database
  As long as the converted result contains the same data, any of the databases listed above can be used for delivery
• Export to Excel
  Exports to .xls and .xlsx (and the OpenOffice equivalents) are allowed
• Export to CSV
  Exports to CSV are allowed when:
  • All fields are escaped in quotes
  • All columns have a header/column name
  • All files use the same field separator, preferably semicolon or pipeline
  • All files are either UTF-8 (without BOM) or Win-1252 encoded
  • All files use Windows (CR LF) line endings

File transfer

Files are allowed to be transferred using:

• WeTransfer
• Dropbox
• Google Drive
• FTP download
• FTP upload (please request an account)

If compression is required, please use any common method such as

• .zip
• .rar
• .7z
• .tar.gz

Data contents

The backup or export should contain at least all data entered by the clinic. If data is not entered by the
clinic, but is required for the system to function correctly, it should be included as well.
This includes (but is not limited to):

Clients and their properties such as

• Addresses
• Phone numbers
• E-mail addresses
• Remarks, warning, flags, options and other settings
• Balance

Patients/animals and their properties such as

• Identifications (transponders, passports etc.)
• Insurances
• Remarks, warnings, flags, options and other settings

Patient histories including

• Sold products
• Notes, protocols, forms etc.
• Reminders/recalls
• Lab results
• Attachments – including the corresponding files
• Appointments

Products and their properties such as

• Pricing (both purchase and sell prices)
• Pricing rules
• Memos, label texts, notes etc.
• Reminder settings and other triggers (mark as spayed/euthanized etc.)
• Stock settings

Invoices

• Invoice lines
•  Payments