Move from legacy security software or spreadsheets with a clear review process. Prepare the data, check the mapping, and plan the team's first site together.
Files you already have. Every import is reviewed before it is written.
A deliberate move, from records to rollout.
1
Prepare the export
Identify the records you need and export them from your existing system. Confirm who owns the export and which fields can be transferred.
2
Map and validate
Match source columns to Attlock fields. Resolve missing or inconsistent data and review the import before creating records.
3
Start with a site
Invite the team, review site instructions, and agree training and rollout support. Check a first site before expanding.
01
Know what is moving
Discuss guards, sites, clients, checkpoints, incidents, and shifts with the team. Available source exports and import support determine the final scope.
Discuss guards, sites, clients, checkpoints, incidents, and shifts with the team. Available source exports and import support determine the final scope.
Review the source record before taking the next step.
02
Resolve issues before import
A matching column name is a starting point. Review required fields, dates, relationships, and duplicates before accepting the mapping.
Data preparation and team onboarding are different jobs. Confirm invitations, access, training, and the first operational check with your company.
Review the source record before taking the next step.
The example on this page uses authored rows: no file is read and no records are created here. Your company admins can import records themselves from the Data Migration tool in the dashboard, and assisted migration, scope, timing, and support are agreed separately.
How an import works. Six steps, and you decide at each one.
01
Choose and upload
Pick guards, sites, clients, shifts, checkpoints, or incidents, then upload a CSV or Excel file. A downloadable template shows the headers if you are starting from a spreadsheet.
You decide: Which record type, and which file.
guards-export.csv
Record type · Guards
02
Match the columns
Columns are matched to Attlock fields for you, and the tool recognises some exports from their headers. A mapping you confirm is remembered in this browser for next time.
You decide: Whether each pairing is right.
Officer emailEmail
Date hiredHire date
03
Clean and validate
Spacing, name and email case, phone numbers, dates, and currency symbols are cleaned first, and the number of fixes per rule is shown before you continue.
You decide: Whether the tidy-up looks right.
Auto-cleaned 14 issues· 2 rows need a fix
04
Review the preflight
The preflight counts what would be created, updated, skipped, duplicated, invalid, or blocked by a plan limit, and writes nothing. Download it as a CSV to review with your team.
You decide: Whether to skip rows with errors, and how to treat duplicates.
18
Create
1
Skip
2
Invalid
05
Import in batches
Nothing is created until you choose Start Import. Records are then written in batches of 200 rows, and you get a summary of what was imported and what was not.
You decide: When to start.
Batch 3 of 4 · Illustrative
06
Review or roll back
A completed import appears in the import history. Roll it back and the records it created are removed and the ones it updated are restored.
You decide: Keep it, or roll it back.
Guards · 18 of 21 importedRoll back
The preflight and the cleaning write nothing.
Rows with errors can be skipped, and that is on by default.
Each import keeps a record of what it created, which is what makes rollback possible.
A completed import can be rolled back.
Know what can move. And what each record needs.
Six record types import today. Each has a few required fields, and some are checked for duplicates before they are created.
Required fields
First name
Last name
Email
Guards. For a guard that already exists, choose to skip, overwrite, or merge.
Duplicate check: Email, employee ID · 20 fields available
Required fields
Site name
Address
Sites. A site name that already exists in your company is skipped.
Duplicate check: Name · 12 fields available
Required fields
First name
Last name
Email
Clients. For a client that already exists, choose to skip, overwrite, or merge.
Duplicate check: Email · 7 fields available
Required fields
Site name
Date
Start time
End time
Shifts. Shift rows are not checked for duplicates, so review them before you import.
Duplicate check: Not checked · 8 fields available
Required fields
Checkpoint name
Site name
Checkpoints. Duplicate checkpoint names in the file are flagged for review.
Duplicate check: Name · 6 fields available
Required fields
Date
Site name
Incident type
Description
Incidents. Incident rows are not checked for duplicates, so review them before you import.
Duplicate check: Not checked · 7 fields available
A guard import can also carry phone, employee id, pay rate, max hours per week, skills, languages, hire date, address, driver's licence, emergency contact. Not part of the import tool: post orders, training records, invoices, documents. Bring those over by hand.
Records in a spreadsheet? Download an Excel template for any of these. It has the right headers, a few sample rows, and an instructions sheet.
Tidied up first. Then checked.
Before validation, the import fixes common formatting problems so you see fewer errors. It shows how many fixes each rule made, so you know what changed before you continue.
Names, emails, and phone numbers are made consistent.
Dates are standardised, including spreadsheet date values.
Currency symbols and placeholder values like N/A are cleared.
Attlock MigrationMigrationAuthored example · No file uploaded
Illustrative values. Review the result before you validate and import.
Review before anything is created. Undo if it is not right.
A preflight before import
See how many rows will be created, need a fix, or will be skipped before anything is written. Download the preflight as a CSV to review it with your team.
Duplicates and conflicts
Duplicates are checked for guards, clients, sites, and checkpoints. For guards and clients, choose whether to skip, overwrite, or merge a record that already exists.
Plan limits, flagged early
Rows that would go over your plan's limits are flagged in the preflight instead of failing halfway through.
Undo a finished import
A completed import can be rolled back from the import history. Records it created are removed, and records it updated are restored.
Only company admins can run an import.
Made for the people who decide. And the people who do the work.
Is it worth the effort, and what is the risk?
Prepare the export
Review the mapping
Invite your guards
Check one site first
Know what switching asks of you. Most of the work is people and decisions, not typing: who prepares the export, who reviews the mapping, who invites the guards, and who checks the first site.
Starter · 5 per site
Professional · 10
Enterprise · Unlimited
Check your plan before you import. The preflight flags rows that would go over your plan's limit before they are created. Starter includes 5 guards per site and Professional 10. Enterprise is unlimited.
Start with one site. Move one site first, review it, then add the next. Plans are priced per site, and every new site starts from the same steps. Start with a 14-day free trial, no credit card.
Your records stay yours. Take your records out as files your team can open and keep: CSV, PDF, or Excel, depending on the record. Payroll provider connections are planned, so a payroll export is a file handoff.
Keep your clients in the loop. Clients can be imported too. In the client app, reports only appear once your team has approved them or sent them for review, so the review step stays in your hands.
Bring us in when it is big. For a larger or multi-site move, our team can plan it with you. Data migration and onboarding and training are part of Enterprise and Talk to Sales plans, with scope and timing agreed with you.
Source exports and field quality decide what can move, so no transfer is promised in advance. Feature availability follows your plan and enabled modules. See what you can export
Continue the workflow.
Questions about Migration & Onboarding.
What to know about getting started, supporting your team, and running your sites.
No universal transfer is promised. The source system, export format, required fields, and record relationships determine what can move. Agree the scope and review the data before importing.
No. The example on this page uses authored rows only. Imports run from the Data Migration tool in your dashboard, where a company admin uploads a file, reviews it, and decides when to continue.
Yes, for a completed import. Records the import created are removed and records it updated are restored. Review the preflight first so you rarely need to.
Company admins run imports. Guards, sites, clients, shifts, checkpoints, and incidents can be imported today. Assisted migration and onboarding and training are part of Enterprise and Talk to Sales plans.
Run your security team in one place.
Schedule shifts, track patrols, and share reports.