Any format. Any state. We analyse it, report on quality, and load it via Raia Protocol. Full rollback if you change your mind — no risk to your existing system.
The process
You do step one. We do the rest.
Export your data.
Get a data export from your current system — spreadsheet, CSV, AppSheet export, proprietary backup, anything. Format does not matter. We have seen them all.
We accept
We analyse it.
We map your fields, identify duplicates, missing values, and inconsistencies. You get a data quality report before anything is loaded — no surprises.
We build the migration.
A versioned migration script is created — the logic, field mappings, and rollback. The script itself goes into GitHub. Your actual data never does. It flows through an encrypted pipeline and your source file is deleted once loading is complete.
Raia Protocol loads your data.
We apply the migration to EstateAigents via the Raia Protocol — our structured, schema-safe import pipeline. Properties, tenancies, contacts, documents — all land correctly.
You go live — or we roll back.
You check everything. If you're happy, great. If not, we run the rollback script: migration tables are dropped, data deleted. Your original system is untouched.
Under the hood
Every migration lives in our database version history as a numbered migration file. Same system we use for all schema changes — battle-tested and reversible.
📁 V041/ — core schema
📁 V042/ — RLS helpers
📁 V099/ — your migration
├── 01_import_yourAgency.sql
├── 02_load_properties.sql
├── 03_load_tenancies.sql
├── 04_load_contacts.sql
└── rollback.sql
# rollback.sql — drops import tables, removes inserted rows
# one file. one command. clean slate.
What is Raia Protocol?
Raia Protocol is our internal import pipeline — a structured, schema-validated process that maps incoming data to EstateAigents' data model. It handles field normalisation, deduplication, relationship linking, and RLS scoping. Your data lands in exactly the right shape.
What we guarantee
Any format accepted.
We have never turned down a data export. Spreadsheet, proprietary backup, SQL dump, PDF list — send what you have.
Quality report first.
Before a single row is loaded, you get a written report on data quality — completeness, duplicates, field mapping. No surprises on go-live.
Git-tracked migration. No personal data in git.
Every migration script is versioned in GitHub — the logic, the field mappings, the rollback. Your actual data never touches git. It flows through an encrypted pipeline, loads into Supabase, and the source file is deleted. GDPR-compliant by design.
Rollback at any time.
Don't like it? Say the word. We run the rollback script. Migration tables are dropped, data is cleared. Your original system was never touched.
Your old system stays live.
We never ask you to switch off your current system before you're ready. Run both in parallel until you're confident. Cut over on your schedule.
Minimal effort from you.
One data export. That's it. We handle the analysis, schema mapping, transformation, and loading. You don't need a technical person on your side.
The rollback guarantee
No lingering data. No manual cleanup. Say the word and the migration is gone.
Go live
You're happy. We confirm. Migration tables are promoted. Your agency is live on EstateAigents.
Or: change your mind
Not sure? You have time. Your old system is still running. Nothing is committed until you say so.
Rollback
We run rollback.sql. Import tables dropped. Inserted rows removed. Your existing data untouched. Clean slate.
Questions
That's fine — most data exports are. We have seen property management data in every state imaginable. We clean it, flag issues, and ask you to confirm before loading. You will know exactly what state your data is in before we touch anything.
No. We can phase it. Start with active tenancies and current properties. Bring over historical records later if you need them. We will structure the migration to match your priority.
A typical migration — 200–500 properties, associated tenancies and contacts — takes 3–5 working days from receiving your export to data loaded and checked. Larger datasets take longer; we will give you an estimate after the quality report.
Properties, tenancy agreements, tenant and landlord contacts, documents, and diary entries where they exist in your source data. We map to our schema and tell you what can and cannot be imported before we start.
The migration creates a numbered import table in your schema (e.g. V099_import_youragency). Rollback drops that table and removes any rows we inserted. Because we never modify your existing data — only insert new rows against your organisation — the rollback is clean and complete.
Yes. All transfers are encrypted in transit (TLS). Your export file is used only for the migration and not retained. We are ICO registered (Z2884909), GDPR compliant, and can sign a data processing agreement on request.
Ready to start?
Send your export to hello@estateaigents.com and we will take it from there.