Where to start
Admin Area → Property Management Flow → Migration
Before you begin
Migration creates native business records after review. Prepare properties and stakeholder identities before dependent tenancy, compliance and maintenance records.
Follow these steps
- Agree source ownership, field meanings and an import order: properties, landlords/tenants/suppliers, then tenancies/compliance/maintenance.
- Choose Stage CSV, Entity type and Source system.
- Upload a CSV no larger than 5 MB or 5,000 staged rows.
- Review the resulting batch, mapping, validation and duplicate counts.
- Commit only after checking normalised data and a representative source sample.
- Verify each committed Target in the native register before progressing to the next entity.
Check the result
You have a traceable staged batch and can reconcile source rows with native target records.
If something does not look right
Staging creates the migration batch, not the native business records. Importing a file is not evidence that its relationships are correct. Delegated users can commit only their own eligible batches.
Questions and answers
Does migration overwrite existing records?
This workflow creates supported native records and blocks detected duplicates; it is not a general overwrite/merge tool.
Does it import uploaded document files?
The listed CSV fields cover record metadata. Source files, signatures and historical delivery evidence are not imported by these CSV columns.
Does importing a customer send a welcome email?
The native customer creation call suppresses welcome email in this migration path. Plan portal onboarding separately.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Map columns, resolve duplicates and commit batches
- Import properties with the Migration Centre
- Import landlords with the Migration Centre
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.