The one-click importers for these systems are switched off for now. They could not do the job safely. The Import Studio replaces them, and it shows you everything before it saves. These pages are for admins.
Steps
- Open the page for your old system. It explains Why it's switched off and lists What you can do now.
- In the old system, export the pupils or people as a spreadsheet. Excel or CSV both work.
- Press Bring pupils into Import Studio where it is offered, or open the Import Studio yourself.
- Choose the file of young people, map its columns and save the mapping. Check it, then save.
- Bring in contacts, goals and consents afterwards as their own files. They need the records to exist first.
- For anything the Studio does not take, press Ask us to import it for you. It opens an email to the help address.
- Do not attach any child's details to that email. Wait for a safe way to send the file.
If it goes wrong
- If the page says the admin role is needed, ask an admin to open it.
- If your export has too many rows, split it. The Studio takes two thousand rows at a time.
- If you are not sure a file is safe to send, add the records one at a time instead.
How it links together
Records brought from an old system become ordinary records here. Anything the Studio cannot take is passed on by asking for help. Staff are invited separately.
- Export
- Import people
- Add contacts and consents
- Invite staff
Why the old importers are off
- Arbor and Bromcom: the old pupil import is off. The Studio can map a pupil spreadsheet into records. Attendance is not imported through these pages.
- CPOMS: the old importer would have recorded every past incident as a new open concern, lost its category and dropped the most serious levels. Safeguarding history is not brought across by this route.
- Lamplight and Makerble: the old importers would have filed every past session as your own unfinished write-up, not as signed-off history.
- Importing contacts from a CSV on its own page now sends you to the Studio, which has a contacts file with checks.
What you can bring in today
- Pupils or people, as a file of young people, with reference codes and a place.
- Their contacts, the goals on their plan and their consents, as separate files.
- One referral at a time, as a Word document or PDF.
What is not brought across
Past sessions, attendance marks and safeguarding incidents from another system are not imported by these routes. Ask for help rather than typing them in, so that they are filed as history and not as new work.
Getting your export ready
Keep one row for each person, with a heading on the first row. Include a reference your old system used, so that the Studio recognises the same person later. Dates are safest typed as day, month and year.
Asking for help safely
The help email names the import you want. Please do not attach children's details to it. A safe way to send the file is arranged afterwards.
Staff are separate
Inviting your team from a spreadsheet is a different job, done by an admin on the staff import page. See the guide to inviting staff from a file.