Switching platforms

Switch NDIS training platforms without losing your records.

The cost of changing platforms is rarely the licence. It is the training history you already hold, and the fear of arriving somewhere new with an empty register. CORA imports what you have in bulk, shows you exactly what it will write before it writes it, and creates nothing behind your back.

Credentials and in-person training records import from a CSV you export from wherever they live now. They land as the same kind of record CORA builds from a fresh upload. The credential register, the due dates and the audit exports are complete from the first day.

Will I lose my training records if I switch platforms?

Not if you can export them. CORA imports credentials and in-person training records in bulk from a CSV. Columns are found by name rather than by position, so an export from another system goes in without rearranging it. You see a full preview of what will be written before anything is saved.

The preview is the plan. What you are shown is re-derived on our side when you confirm, rather than taken on trust from the browser. The only thing sent back is the original file.

What format does the import file need to be in?

A CSV with a header row. Two columns are required, the worker's email and the credential or training name. Category, issuer, date completed and expiry are optional. Column names are matched against a list of aliases, so headings like course, qualification, issued by, valid until and renewal date are all understood. Dates are read in Australian order, so 03/07/2026 is 3 July, and ISO dates are accepted too.

You do not reorder anything. A fixed column order is a trap for anyone building a file in a spreadsheet, so position is ignored and only the heading matters.

How many records can I import at once?

Up to 2,000 credential or training rows in one file, and up to 5,000 workers in one staff file. Over the cap the whole file is refused rather than part-loaded, so you are never left guessing which half landed.

Will importing create new staff accounts and charge me for seats?

No. A credential row is matched to a worker who already exists, by email, ignoring capitals. An email that matches nobody is reported back to you by row number rather than quietly turned into a worker. Adding a person consumes a paid seat, and that stays your decision. Load your staff list first, then the records.

What happens if I run the same import twice?

Nothing changes. A row counts as already recorded when the same worker holds a credential with the same name and the same date completed. A genuine renewal carries a new date, so it lands as a new record and the register keeps the history rather than overwriting it.

Do in-person training records go in the same place as courses?

Yes. An in-person training record and a credential are the same kind of row in CORA, separated only by a category for display. The manual handling day you ran in March lands in the same register as a first aid certificate and a CORA course. It feeds the same due dates, reminders, evidence and exports.

That is what makes day one look like year four. Everything your team already holds is in the register from the start, so the due dates and the audit exports are complete rather than beginning at zero.

Coming from eTrainU or NGO Training Centre?

Most providers who move to CORA are coming from eTrainU, from NGO Training Centre, or from a spreadsheet someone has kept by hand. The mechanics are the same for all three. Export what you hold, send us the file, and we map your column headings to ours before anything is written.

We make no claim about those platforms on this page. What we will tell you is what happens to your records once they arrive here, which is the part you are actually buying.

Your file does not need to look like ours. Column headings are matched against a list of names rather than a fixed order, so whatever your export calls a course, a qualification or a renewal date, it is understood.

What order should I do the move in?

Staff first, then records. The staff file creates the people and respects your seat count. The credential file attaches history to people who already exist. Doing it the other way round means every row reports an unmatched email.

How long does a migration take?

We do it with you rather than handing you a template. Send us what you hold and we will turn the import around within 24 hours. Most of the work is on our side, because matching your column headings to ours is the part that takes judgement.

Send us what you hold

Export your records from wherever they sit now, including a spreadsheet, and send the file. We will map your columns, show you the preview and turn it around within 24 hours.

Request a demo See pricing