Where to start
Admin Area → Property Management Flow → Migration → Stage CSV → Compliance records
Before you begin
A resolvable property reference and compliance_type are required. Use valid ISO dates where supplied.
Follow these steps
- Prepare one entity CSV using the supported columns below.
- Choose Compliance records as Entity type, identify the Source system and stage the file.
- Map the source columns and inspect every normalised field.
- Resolve missing relationships and duplicate warnings before commit.
- Commit valid rows in bounded batches and open each Target in its native register.
Check the result
The target record and relationships match the reviewed source row. Imported records use approval_status draft, even if source status indicates compliance. Review original evidence through the native Compliance screen; CSV metadata does not approve or authenticate a certificate.
If something does not look right
If a dependency cannot be resolved, import or correct it first and revalidate. Do not replace an actual email or property identity merely to get a row past validation.
Questions and answers
Which columns are supported?
property_reference, compliance_type, title, status, issue_date, expiry_date, certificate_number, engineer_name, engineer_registration_number, notes.
Can I upload an Excel workbook?
This importer accepts CSV. Export the intended worksheet as a plain CSV and review dates, identifiers and leading zeros.
Can I remove a committed batch to undo the import?
There is no general migration rollback control in this screen. Committed targets are native business records; arrange any correction through the authorised native workflow.
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
- Plan and stage a governed migration
- Map columns, resolve duplicates and commit batches
- Import properties 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.