Import tenancies with the Migration Centre
Property reference, an email resolving an existing tenant account and tenancy_start_date are required.
Before you start
Property reference, an email resolving an existing tenant account and tenancy_start_date are required. End cannot precede start. Amounts must be non-negative; supplied landlord email must resolve.
Follow these steps
- Prepare one entity CSV using the supported columns below.
- Choose Tenancies 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 it worked
The target record and relationships match the reviewed source row. The native onboarding service creates the tenancy. Accepted workflow stages are draft, context_selected, parties_confirmed, compliance_snapshot_refreshed, agreement_preparation, ready_for_review, approved and notifications_sent. Status is draft, active, completed or cancelled; unsupported values fall back to draft.
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, tenant_email, landlord_email, tenancy_reference, move_in_date, tenancy_start_date, tenancy_end_date, rent_amount, deposit_amount, holding_deposit_amount, deposit_scheme, workflow_stage, status, 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.