How to bring your data from another system to GENNO
If you already use another system or keep everything in spreadsheets, you don't need to type your history again. You send what you have and the GENNO team migrates it to your account, on demand.
Before you start
- If your data fits the GENNO template, you import it yourself on the web, in Settings › Organization › Import data (see below). A database from another system, a backup or a spreadsheet in another format: the GENNO team does the migration, case by case.
- The data goes into your stud farm's or clinic's account. If you don't have an account yet, see how to create one.
- You don't need to tidy anything up first. Send what the old system gives you, as it is.
What you can send
| Type | Examples |
|---|---|
| Database backup | The old system's backup file: SQL Server, PostgreSQL, MySQL, Firebird, Access and others. |
| Spreadsheets | Excel, CSV or Google Sheets with horses, clients, breedings or accounts. |
| Exports | Files the system creates when exporting: CSV, XML, JSON or TXT. |
| PDF reports | They help the team check the numbers, even when they can't be imported. |
What usually comes along: horse records and pedigrees, owners, reproduction history (exams, breedings, inseminations, embryos, pregnancies and foalings), semen, visits and vaccines, and accounts receivable. What actually comes in depends on what the file holds: the analysis shows that first.
What the team's migration tool reads on its own today: clients and owners, properties, horses (with sire, dam, breed and owner), visits, vaccines, reproductive events (breedings, inseminations, ovulations) and pregnancies. Semen, stock and finance come in case by case, agreed in the ticket.
If all you have is a spreadsheet: the GENNO template
When the data lives in a loose spreadsheet or on paper, the fastest path is to fill in the GENNO template: a workbook with one sheet per kind of data and the headers GENNO recognizes by itself.
- Download the GENNO migration template (xlsx).
- Read the Leia-me sheet and fill in only the sheets you need: Clientes (clients), Propriedades (properties), Animais (horses), Atendimentos (visits), Vacinas (vaccines), Eventos reprodutivos (reproductive events), Gestações (pregnancies) and Embriões congelados (frozen embryos, with the donor, the stallion and the tank position: tank, rack and position).
- Don't change the headers. Each one has a comment with the explanation, the example and the accepted options; the light-green columns are required.
- Dates as dd/mm/yyyy (or yyyy-mm-dd), numbers with a comma or a dot, sex as Macho (male) or Fêmea (female); English words such as mare and stallion are also understood.
- Sire, dam, mare, stallion and horse: write the registration or the name exactly as it is on the Animais sheet (or as already registered in GENNO). Owner: the name or the document as on the Clientes sheet; if it doesn't exist, GENNO creates the client from the name.
- Breed: the name as in GENNO's catalog (Mangalarga Marchador, Quarter Horse...). Outside the catalog, it is kept as text.
- Import it yourself on the web (see the section below) or send the filled template through the ticket, like any other file.
Spreadsheets that don't follow the template also work: the team sets, column by column, what each one becomes in GENNO.
Import it yourself on the web (GENNO template)
With the template filled in, whoever can change the organization (the administrator, by default) imports without opening a ticket:
- On the web, click Settings and, under Organization, Import data.
- Click Download the template if you don't have it yet, and fill it in as explained above.
- Click Upload file and pick the spreadsheet. GENNO reads the file and the status changes to Ready to check.
- Click Check. GENNO simulates the import row by row, without saving anything, and shows how many records are new, updated or skipped, plus the errors and warnings.
- If there are errors, click See the problems (or Download the findings), fix the spreadsheet, upload it again and check. Warnings don't block the import.
- With no errors, click Import. When it finishes, the status changes to Imported.
Only the GENNO template goes through here: a tab GENNO doesn't recognize stops the check with its name. If something went wrong, click Undo this import and type the organization name: what the import created is deleted and what it changed goes back to how it was. The last import can be undone for 7 days.
Request the migration
- On web.genno.app, click Support in the menu.
- Click Migrate data from another system. The New ticket window opens with the subject, the Data migration category and a checklist already filled in.
- In What happened?, complete the checklist: the old system's name, the file format, the approximate size and what you want to bring.
- Click Open ticket.
You can also ask on the support WhatsApp or on the Data migration page of the website.
The backup holds your clients' and horses' data. Wait for the team to reply in the ticket with a secure way to send the file.
What happens next
- Sending: the team replies in the ticket with the way to send the file.
- Analysis: the team opens the database and shows in the ticket what comes into GENNO, what stays out and the timeline.
- Validation: before anything is written, the tool checks line by line and the team sends the list of what needs fixing (a date it can't read, a horse that doesn't exist, a breed outside the catalog). You fix the file or agree with the team on what to do.
- Sample: with your go-ahead, the team imports a part so you can check the horses and their history in your account.
- Full migration: the team imports the rest and lets you know in the ticket when it's done. Importing the same file again, corrected, updates the records instead of duplicating them.
Follow everything on the Support page. When the status is Waiting for you, the team needs a reply from you. See how to follow a ticket.
The old system and the original file stay as they are. The copy sent to the team is used only for the migration and is deleted within 30 days. Within that same period, if something went wrong, the team undoes the whole migration: what it created disappears and what it changed goes back to how it was.
Common problems
The old system has no export option. Open the ticket anyway. The system's own backup is often enough; when it isn't, spreadsheets and reports help.
I'm still using the old system in the meantime. That's fine. Before the full migration, agree on a date with the team in the ticket so nothing is left out.
A horse came in with wrong data. Reply in the ticket with the horse's name and what's wrong. For a one-off fix, you can also edit the horse. If it's widespread, the team undoes the migration, fixes it and imports again.
The horse's breed shows as "outside the catalog". The spreadsheet had a name GENNO doesn't recognize (an abbreviation, a different spelling). The text is kept; open the horse and pick the breed from the list.
Next steps

Didn’t this article solve it?
Talk to the GENNO team. Tell us what you were doing and, if you can, send a screenshot.