Switching SEND software in UK schools: the one-click migration myth

Call it the one-click migration myth: moving special educational needs and disabilities (SEND) software is not a silent upload. The real test is whether the new system gives staff one usable view of the pupil, costed provision, current plan, passport, evidence, review history and next action, while showing what needs checking.

A good migration moves three things together: the source documents, the structured working record and the day-to-day process around that record. That may include SEN Support Plans, profound and multiple learning difficulties (PMLD) plans, costed provision, pupil voice, review dates, pupil passports, reporting, staff permissions and the history that explains how support has changed.

The school should not have to work this out alone. MeritDocs provides guided setup and onboarding at no extra cost. The team can help prepare existing Portable Document Format files (PDFs), Word files, images and pupil data for best-fit import, explain what has mapped, and help staff review the result before it becomes part of the live workflow.

The sensible goal is not a silent one-click transfer. It is a controlled move where staff know what came across, what needs checking, where the original sits, and how the new record will be used after go-live.

What actually needs to move when a school changes SEND software?

A SEND migration is more than uploading a folder of PDFs. It is a move from one way of storing and reviewing information to another.

The first migration scope may include:

• the SEND register and basic pupil details;
• current SEN Support Plans and other support documents;
• PMLD plans or setting-specific documents where relevant;
• Education, Health and Care Plan (EHCP)-related records held by the school;
• identified needs, outcomes, targets, costed provision and provision detail;
• review dates, actions and the most recent decision;
• pupil, parent, staff and professional contributions already recorded in documents;
• pupil passport or profile information that staff need in daily practice;
• photographs, scans or older paper plans that still provide useful context;
• document history and the original source files.

Not every historical record needs to become an active record. Some files may have reached the end of their useful operational life. Some may need to be retained for a defined period but kept outside the daily workflow. Others contain context that staff will need at the next review or transition.

That decision belongs to the school. A provider can make the work easier, but it should not decide the school's retention policy or quietly discard information during an import.

The Department for Education's guidance on data protection in schools recommends auditing the personal data a school holds and deciding what needs to be kept, destroyed, moved from paper to electronic format, or retained in another form. It specifically includes special educational needs within the pupil data groups schools should review. Read the DfE record keeping and management guidance before agreeing the migration scope.

A SEND system needs to do more than store the old files

The new platform has to support the work that starts after the import. Otherwise the school has simply moved its filing problem.

Keep the pupil record usable

A SEND register is useful when it helps the right person find the right information quickly. Staff may need the current plan, the latest review date, the pupil's relevant needs, recent changes and the document that explains what should happen next.

A useful profile keeps source statements visible and separates reviewed, historical, current information.

Turn recorded evidence into a working plan

Support documents should give staff something they can use, not simply a polished description of a pupil. The plan needs to connect identified need with outcomes, targets, provision and review arrangements.

A system can help staff turn recorded evidence into a structured SEN Support Plan or PMLD plan, but the generated document still needs professional checking. The wording should reflect the pupil's evidence, preserve relevant qualifiers and avoid inventing certainty where the source material is incomplete.

This is where evidence-grounded drafting is more useful than a generic statement bank. It can give staff a structured starting point while leaving the final judgement with the special educational needs coordinators (SENCOs) and authorised staff.

Keep pupil and family voice visible

Pupil voice, parent views and professional advice can disappear when information is copied between forms. During a migration, check where each type of contribution will sit and whether staff can distinguish a direct quotation from a professional observation or an older summary.

The record should preserve the source meaning. Flag content that does not fit instead of filling gaps with generic SEND language. MeritDocs keeps source material available when staff review imported content.

Connect provision to review

A complete SEND provision workflow connects the map to the pupil record. Staff need to know what each provision costs, what it is intended to achieve, what evidence will be reviewed, who owns the next action and when the review should happen.

Before go-live, check that the new workflow can show the relationship between need, outcome, provision and evidence. It should also make it possible to see what changed at the last review rather than treating every new plan as an isolated document.

Keep passports and profiles current

A pupil passport is useful in a handover, cover situation or classroom context only if staff trust its currency. A forgotten static PDF is not a dependable current record.

Ask who can draft, review, publish, update, version, archive and print it, and how staff will identify the current version.

Give each role the right view

Class teachers, teaching assistants, SENCOs and senior leaders do not all need the same level of access. The school should be able to set permissions deliberately and explain who can view, edit, review, approve or export a record.

Access control is part of the migration plan, not a setting to leave until later. The first pilot should include the people who will use the records in ordinary school work, not only the person coordinating the import.

A safe seven-step migration plan

1. Decide what the new system needs to do

Start with the workflow, not the export button.

Ask:

• Which pupils need to be in the first migration group?
• Which documents do staff use every week?
• Which records need review dates and follow-up actions?
• What should a class teacher, teaching assistant, SENCO or senior leader be able to find?
• Which historical files are useful context rather than active records?
• How will the school use the SEND register, pupil profile, support plan and passport together?
• What would make staff say the new system is easier to use after the first month?

A small first cohort is usually more useful than trying to move every record on day one. It gives the school a chance to test the mapping, permissions, naming conventions, document versions and review process before the wider rollout.

Define pilot tasks: find the current plan, identify the review, understand the provision, check the evidence and export a copy.

2. Find out what can be exported

Before signing, ask the current provider or administrator what the school can export and in which formats.

You may receive:

• a comma-separated values (CSV) or spreadsheet export;
• PDFs;
• Word documents;
• image files or scans;
• a ZIP folder of documents;
• a report that contains some information but not the full underlying record.

Ask for a sample export before planning the whole migration. A sample shows whether pupil identifiers are consistent, whether review dates are included, whether the files are readable, and whether the source contains the information staff actually use.

Keep the original export in a controlled location. Do not overwrite it with cleaned files. The original is your reference if somebody later asks what was supplied, what changed, or why a particular record was not imported.

3. Prepare a simple migration pack

A migration pack does not need to be complicated. It should tell the implementation team what each file is and what should happen to it.

Include:

• the school or trust name;
• the first pupil cohort;
• a secure list of the relevant pupil identifiers;
• the file types included;
• the document types the school recognises;
• any known naming problems or duplicates;
• records that should be archived rather than imported;
• the staff members who will review the first import;
• the roles and permissions those staff need;
• the target date for the pilot and the intended go-live window.

Do not send pupil data over ordinary email just because it is convenient. Agree a secure transfer route with the provider and make sure the school's data protection lead knows what is being transferred, why it is needed, and who will have access.

4. Map source material into the new structure

Every SEND system has its own fields and document structure. Schools also use different templates, headings and local terminology. Migration is therefore not simply a case of matching file names.

A useful mapping process should answer questions such as:

• Where does the pupil's voice go?
• Where are parent views and professional advice kept?
• Which section contains the identified need?
• Where are outcomes, targets and provision recorded?
• How are review dates represented?
• What happens to a paragraph that does not fit one new field?
• Which source files remain available for reference?
• How will the school tell the current version from an old version?

MeritDocs can import PDFs, Word files, images and pupil data using best-fit mapping. Its purpose is to give staff a structured starting point while keeping the original meaning visible. SEND documents vary between schools and local authorities, so imported content can need review. Hiding those exceptions creates risk, not removing it.

Preserve partial information and uncertainty. A missing field should not become a confident-sounding sentence because the new template has a blank space.

5. Review warnings and unmapped content

This separates a responsible migration from a tidy-looking mess.

The reviewing staff should be able to see:

• which records imported cleanly;
• which fields were matched with lower confidence;
• which content needs a human decision;
• whether a pupil has duplicate or conflicting records;
• whether any content did not fit the new structure;
• where the original document can be opened for comparison;
• which version will become the current working record.

Do not approve an import just because the new record looks polished. Check a small number of records in detail. Include a straightforward record, a long record, a scanned document, a record with several contributors, and one with unusual local headings.

The purpose of the import is to reduce retyping while protecting the information that matters. Staff still need to confirm that the record is accurate and current.

For a closer explanation of why this matters, read Why unmapped content matters when schools import SEND documents.

6. Make the imported record part of the school workflow

An imported record is not finished when it has been approved. The school should now decide how it will be used.

For the first cohort, check that staff can:

• find the current pupil record and support document;
• see the review date and the next action;
• understand the link between need, outcome, provision and evidence;
• create or update a structured support document from recorded information;
• keep the pupil passport or profile current where one is used;
• assign review or approval responsibility to the right staff;
• see the history when a document has changed;
• export a usable copy when a meeting, transition or request requires one.

Agree the document lifecycle: draft, approved current version, review history and archive rules.

7. Run a pilot, then agree the cutover

A pilot should use real enough material to expose problems, but small enough that the school can correct them without panic.

A useful pilot might include:

• one year group or phase;
• a mix of SEN Support and EHCP-related records;
• current documents and a small amount of history;
• different document formats, including at least one scan;
• the staff who will actually use the records;
• at least one review or update completed in the new workflow;
• a test of permissions and export.

Ask staff to complete ordinary tasks, not just admire the imported records. Can they find the current document? Can they identify what needs review? Can they create a new document from the evidence available? Can they see what changed since the last version? Can they export a copy? Can an authorised colleague understand the record without asking the SENCO to explain where everything is?

If systems run in parallel, agree which one is the source for new changes and set an end date.

Before go-live, agree:

• the date after which new work starts in the new system;
• who can edit, review and approve records;
• how urgent changes are handled during the transition;
• when the old service becomes read-only or is closed;
• where the original export is retained;
• who staff contact when they find a problem;
• when the first post-go-live review will happen.

What guided setup at no extra cost should include

Free setup should mean more than sending a login link and a help article.

For a school moving to a new SEND platform, the setup conversation should cover the records being moved, the first cohort, the import format, the document types the school uses, the staff who will review the result, the permissions they need, and how the new workflow will handle review dates, current versions and exports.

The provider should prepare files, explain warnings, support review and make approval responsibilities clear. Approval remains a school decision.

MeritDocs brings migration into the wider SEND provision workflow. It keeps costed provision, pupil passports, plans, reviews, reports and controlled records connected, while the Documents Hub groups information by pupil, makes review dates visible and supports export. Staff can use recorded evidence as the starting point for structured SEN Support Plans and PMLD plans, and can compare imported content with the original source before approving it. The product is browser-based, so staff do not need a separate installation on every school device.

The support is available at no extra cost. Ask any provider to state clearly what setup, migration help, training and follow-up are included before you compare prices.

Every customer can start with a 28-day free trial. Use it to test a representative migration sample, let staff complete real tasks, and find the exceptions before a wider commitment.

Security, access and leaving the old service

SEND records contain sensitive information about children and young people. Migration is therefore a data protection exercise as well as a technical one.

Ask the provider:

• Is the school the controller and is the provider acting on the school's instructions?
• Is a data processing agreement in place?
• What data is transferred, where is it processed, and who can access it?
• How will the provider support the school's Data Protection Impact Assessment (DPIA) and data flow records?
• How are files transferred securely?
• How are access levels set for SENCOs, teachers, teaching assistants and leaders?
• Are sign-ins, views, edits, approvals and exports recorded?
• What happens to the original files after the import?
• How long are records retained if the school stops using the service?
• Can the school export its records in a usable format?
• What is the process for deletion at the end of the relationship?

The Information Commissioner's Office (ICO)'s guidance for education technologies says schools should carry out due diligence when procuring technology and understand the responsibilities of the school and provider. Its edtech guidance also points to the importance of clear contracts, data flow mapping, minimisation, retention and DPIA work. The ICO guidance for education technologies and schools is a useful starting point.

MeritDocs encrypts pupil data before storage, processes data in the UK and European Union (EU), applies school-wide two-factor authentication, controls access and records activity in an audit trail. Schools can export their data. These are implemented product controls. They do not replace the school's own Data Protection Act (DPA), DPIA or procurement checks, which should still confirm the exact processing, retention, subprocessor and deletion terms.

The SEND Code of Practice is also worth keeping in view. A software migration does not change the school's duties to involve children, young people, parents and relevant professionals in the graduated approach. It should support the record of that work, not replace it.

A practical migration checklist

Before the school switches, confirm that:

• the first pupil cohort is agreed;
• the school has a copy of the original export;
• the transfer route is secure;
• retention and archive decisions are documented;
• the document types and local headings have been explained to the provider;
• imported records show warnings and unmapped content where relevant;
• a mixed pilot has been reviewed by school staff;
• staff know where to find current documents and review dates;
• the relationship between need, outcome, provision and evidence is clear;
• roles, permissions and approval responsibilities have been checked;
• current and archived versions are distinguishable;
• the old system's notice period and closure process are understood;
• the new provider has confirmed what setup and support are included;
• the school has tested an export from the new system;
• staff know how to get help after go-live;
• the first post-go-live review is booked.

Frequently asked questions

Can we migrate from a provision map or another SEND service?

Usually, yes, provided the school can export the information or supply readable PDFs, Word files, images or other records. The exact result depends on the quality and structure of the source data. A sample export and a small pilot will tell you more than a generic promise made during a sales call.

Will staff have to retype every SEND document?

They should not have to retype everything. Import and mapping should reduce repeated data entry. Staff will still need to review records, resolve exceptions and confirm that information is accurate and current. Avoid any provider that treats a silent import as proof that nothing was lost.

What happens if our documents use different headings?

That is common. A best-fit import can place source content into a new structure while flagging material that needs a human decision. The school should be able to compare the new record with the original rather than accepting a clean-looking document on trust.

Can the new system support more than provision mapping?

It should. Provision is one part of the SEND workflow, but the platform should connect it to cost, the current pupil record, structured support documents, evidence, review dates, document versions, permissions, pupil passports and usable reports and exports. A map that is disconnected from the plans and reviews around it will not solve the whole provision-management problem.

How long does SEND software migration take?

There is no honest universal answer. The timeline depends on the number of pupils, file formats, document variation, review capacity and the school's chosen cutover date. Start with a sample, measure the review work, then set the wider timetable.

Can we run the old and new systems in parallel?

Yes, where the school needs that safety net. Keep the period controlled and agree which system is the source for new changes. Running two systems indefinitely creates its own version-control problem, so parallel use should have an end date.

Is guided setup included with MeritDocs?

Yes. MeritDocs provides guided setup and onboarding support at no extra cost. The team helps schools prepare their migration, set up the workflow, review the import and get staff started. The school remains responsible for approving the records and its own data protection decisions.

Can every school try the platform before switching fully?

Every customer can start with a 28-day free trial. A sensible trial uses a representative sample of the school's records and asks staff to complete real tasks, including finding, reviewing and exporting documents.

Switching does not have to mean starting again

The fear around migration usually comes from a reasonable place. Schools have already put time into their records, and nobody wants to lose context, retype years of work, or introduce a new process during an already busy term.

A careful migration deals with that risk in stages. Preserve the source. Start with a representative sample. Show the exceptions. Let school staff approve the result. Connect the current plan to provision and review. Make permissions clear. Set a cutover date. Keep the new records easy to find and export.

That is the standard to look for when you compare SEND software. MeritDocs helps schools move existing records into a structured provision workflow covering maps, passports, plans, reviews and reporting, offers guided setup at no extra cost, and gives every customer a 28-day free trial. The software supports the process, but professional judgement stays with the people who know the pupils and the context.

Talk to the MeritDocs team about your migration, or use the trial to test a real sample before you decide what to move.

Sources and further reading

• SEND code of practice: 0 to 25 years, Department for Education and Department of Health and Social Care.
• Data protection in schools: record keeping and management, GOV.UK.
• FAQs for education technologies and schools, Information Commissioner's Office.
• Why unmapped content matters when schools import SEND documents, MeritDocs.
• MeritDocs security and data protection, MeritDocs.