Import from Kintraks

OmniBurrow ships a Kintraks profile, so a Kintraks animal export is detected from its columns and mapped without manual column matching. Kintraks-only details that have no OmniBurrow field of their own — call name, suffix, health, and custom fields — are kept in the rabbit's notes rather than dropped. Nothing is written to your herd until you approve the review screen.

What comes across

Kintraks exports one file: the animal list. Every rabbit in it becomes a rabbit record.

Kintraks column	Becomes
Name (or CallName if Name is empty)	Rabbit name
Tag / Ear Tag / Tattoo	Ear tag
Sex	Sex — buck or doe
DOB / Date of Birth	Date of birth
Breed	Breed, matched against the ARBA catalog
Colour / Color	Variety, matched against that breed's varieties
Father / Sire	Sire, matched by name
Mother / Dam	Dam, matched by name
Prefix	Breeder name
Cage	Cage

Notes, CallName, Suffix, Health, and any Custom Field 1, Custom Field 2… columns are gathered into the rabbit's notes, each on its own labelled line.

A row needs a name or an ear tag to import; rows with neither are skipped.

Import your herd before your pedigrees

Do this import first, then pedigree import. Pedigree import links an extracted ancestor to a rabbit you already own when the ear tag or registration number matches exactly — getting the herd in first is what stops you ending up with two copies of every grandparent.

Export from Kintraks

OmniBurrow does not drive the other program, so what matters is the file you end up with: a delimited export of the animal list, saved as .csv, .tsv, or .txt. Comma, semicolon, tab, and pipe separators are all detected automatically.

Keep the original column names. Detection needs a Name column plus at least two of CallName, Suffix, and Health — that trio is what tells a Kintraks file apart from a similar-looking export from another program. Rename them and OmniBurrow falls back to manual mapping, which still works but costs you the auto-detection.

Files up to 10 MB are accepted; if yours is larger, export in parts.

Import into OmniBurrow

Web App

1. Go to Dashboard → Import data and use the first section, Move data from another program.
2. Drop the Kintraks file into the drop zone, or click to browse for it.
3. OmniBurrow detects the profile and matches breeds, varieties, parents, and existing records, then shows the review screen.
4. Check the review, then click Import to commit.

Mobile App

1. Open More → Import, then Move data from another program.
2. Tap Choose import file and pick the Kintraks file.
3. OmniBurrow shows the detected profile and its confidence, the row and column counts, and a preview of the first few rabbits. Tap Review and import.
4. Check the review, then tap Import.

This works offline — the file is read and the records are written on the phone, and they sync the next time you have signal.

Review before committing

The review screen shows exactly what will be created before anything is written.

• To import — how many new rabbits will be created.
• Already in herd — rows that matched a rabbit you already have. They are skipped, not overwritten. A row matches on registration number first, then ear tag, then name plus date of birth.
• Parents linked — how many sire and dam links resolved.

Warnings above the list flag anything worth a look:

• A breed that did not match the ARBA catalog is kept as free text.
• A variety that did not match is saved as a custom variety.
• A parent link that could not be resolved is left empty rather than guessed, and a parent name that matched more than one rabbit is flagged as ambiguous.
• Rabbits whose breeder name came from the Prefix column are called out on the mobile review so you can confirm the prefix really is the breeder.

Parents are matched by name here, not by a record number, so spelling matters. If a parent is written as Prefix Name in one place and just Name in another, OmniBurrow still finds it; a genuinely different spelling is left unlinked for you to fix.

Related

• Program import
• CSV field reference
• Import errors