Hi @wojcika ,
It looks like that link lost the "l" off the end, so here is an updated link for those who may be finding this thread later: SIS Import Format Documentation - Canvas LMS REST API Documentation
You'll be using the accounts.csv data format that is listed on that page.
If you use the provisioning report as an export to work from and modify, you'll have all of the following field headers:
| canvas_account_id | account_id | canvas_parent_id | parent_account_id | name | status | created_by_sis |
But as the documentation notes the only *required* fields for an accounts.csv import file are:
account_id
parent_account_id
name
status
The next info you didn't ask for, but it crossed my mind and I felt like sharing...
I highly recommend establishing a naming standard for account_id, so that it makes some sense to you either where it lives in the structure or what it contains. For myself I chose to hold subject codes as their own account_ids (ex: MAT = Mathematics), since they contain the majority of the actual course shells, and assuming that some day they move within the structure. The structural/organizational sub-accounts may not change as much (or maybe they will!) so I used a naming convention that included more details about the nesting since the parent_account_id only gives you one level up (ex: CAES_DHS_HE = College of Ag & Environmental Science, Division of Human Science, Department of Human Ecology).
And our decision around when to provide a sub-account layer were primarily. 1) If there might be the need or desire to provide a sub-account administrator at that level. 2) If there might be a need to report on Outcomes, share rubrics, etc. at that level 3) If there might be the need to install a purchased LTI tool for just a subset of course shells.
This discussion post is outdated and has been archived. Please use the Community question forums and official documentation for the most current and accurate information.