Import spreadsheets without surprises
Use templates, validation, row reports and the supported undo window.
Takadar uses a shared import workflow for supported datasets: Choose → Upload → Map → Validate → Confirm → Report. Start from the import action for the resource you want to load rather than reusing an unrelated template.
Prepare the right workbook
Download the setup workbook from an import page. It groups supported sheets in loading order, with examples or current institution data where available. Use the template’s identifiers and lookup values rather than guessing names.
Load dependencies first: academic structure before placements and offerings, fee types before fee plans, hostels before rooms and room allocations, vehicles and routes before transport assignments.
Validate before confirming
- Choose the resource and relevant context.
- Upload the file and map its columns.
- Read the validation report, including warnings and row-specific errors.
- Correct the file or export failed rows as supported, then validate again.
- Confirm and retain the final report so accepted and rejected rows are accounted for.
An uploaded fee plan starts as a draft and bills no one until activation. Admissions-score imports update existing applications; they do not create applications from unmatched rows. Hostel allocations reject a full room or a student who already has a room. Timetable previews flag teacher and room conflicts.
Correct a completed import
Supported shared imports offer a 24-hour undo window. Review the batch and its actual available action; do not treat undo as a general rollback of later work. Preserve your original file and the result report.
Use past-record imports for closed academic years. Use opening balances for existing debt, not a reconstructed set of old payments. For large or mixed datasets, first validate a representative subset to confirm identifiers and relationships before loading the full file.