Preserve useful context
Keep agreed historic records available so teams can understand concerns, actions and outcomes over time.
Changing platform should not mean starting again.
Your historic records provide essential context for current decisions. Our migration team helps you move that history into RecordMy, agree how source fields should map and check the result before your team relies on it.
Hundreds of completed data migrations across different organisation types and source systems.
24–48 hours is a typical launch window for standard migrations once the required files are available.
Map data deliberately
Align people, categories, dates and record types with the way your new RecordMy environment is configured.
Review before sign-off
Technical checks and customer validation help confirm that the agreed data is ready for operational use.
A clear route from export to launch
Every migration begins by understanding the source data. We then agree the scope, transfer route, mapping and checks before your team starts using the imported records.
Scope the move
We review your source, export format, data volume and any priorities for the new environment.
Transfer securely
Your authorised team provides the agreed export through the secure transfer route we confirm with you.
Map and import
We map agreed fields and categories, import the records and carry out technical validation checks.
Review and launch
Your team reviews the result, we address agreed corrections and you move into RecordMy with support.
What can move into RecordMy?
Migration scope depends on what your current system can export. We work from the available source data rather than assuming every platform stores or exposes information in the same way.
Common source formats
We have experience working with structured exports from a range of safeguarding and record-management sources.
- Existing safeguarding and concern-recording systems
- Structured spreadsheets and CSV exports
- Cloud documents and agreed supporting files
- Multiple datasets for trusts and multi-site organisations
Commonly migrated information
The final mapping is tailored to the fields available and the configuration agreed for RecordMy.
- People records and identifying references
- Historic concerns, actions, outcomes and dates
- Categories, tags and relevant chronology context
- Agreed notes, evidence and supporting information
Before work begins: we confirm what is included, identify anything that cannot be transferred reliably and agree how the imported information will appear in RecordMy.
More than a data import
Moving platform is also an opportunity to make sure RecordMy reflects how your organisation records, reviews and acts on concerns.
Configuration
Set up terminology, categories, forms, permissions and workflows around your organisation.
Onboarding and training
Help administrators and staff understand the new environment and establish a confident launch.
Ongoing support
Get help after launch as questions arise, teams develop their processes or requirements change.
Can we bring our existing safeguarding history?
Yes. RecordMy can migrate structured safeguarding records from existing systems, spreadsheets and cloud documents. The exact scope is confirmed after we review the available export, its structure and the quality of the source data.
How long does a migration take?
Most standard customers can be onboarded within 24 to 48 hours once the required information and export files are available. Complex datasets, multiple sources and bespoke mapping are planned separately and commonly complete within two weeks.
How do we know the import is correct?
We map and import the agreed data, carry out technical checks and then support your authorised team to review the result. Any agreed corrections are addressed before the migration is signed off.
Tell us what you need to move.
Share your current data source, approximate record volume and preferred timescale. We’ll outline the likely migration route and any information needed to scope it properly.