Plan your migration with clear review points.
Discuss your source data, implementation priorities and cutover decisions with the Sentus team. Scope and timing are confirmed in writing.
Discuss the source you use today.
These sources can be assessed for fit. Available exports and migration coverage depend on the agreed scope.
AppFolio
Assess property, unit, resident, lease, work-order and accounting exports.
Buildium
Review the available export tree, including statements where relevant.
RealPage
Review available portfolio exports and their scope.
Yardi (Voyager / Breeze)
Assess data sets, general ledger mappings and chart of accounts.
Entrata
Review exports and custom fields for mapping.
Property Meld
Assess maintenance history and vendor relationship records.
From discovery to a reviewed cutover decision.
These example day ranges illustrate the sequence; timing depends on the agreed scope.
- Day 0-3
Discovery and written scope
Review your source, priorities and secure transfer arrangements, then agree the proposed migration scope.
- Day 4-7
Data assessment and validation
Review mappings and exceptions with your team, including the Management, Resident and Maintenance workflows in scope.
- Day 8-11
Workflow review
Review intake, escalation and communication preferences. Consent records and any outbound activation require separate review.
- Day 12-14
Cutover decision
Review readiness, parallel operation and rollback arrangements before deciding on cutover.
Confirm your written scope before committing.
Data reconciliation
Confirm the records, fields and reconciliation approach included in your scope.
Parallel operation
Agree whether parallel access is available and how long it is needed.
Commercial start
Confirm migration pricing and billing start in your agreement.
Rollback
Agree a rollback approach and decision points before cutover.
Questions to address before a switch.
What will switching require?
Review responsibilities, timing and the work your team needs to contribute before committing.
How will data be checked?
Identify important records and exceptions, and agree how the team will review reconciliation.
What happens to compliance records?
Identify relevant records and retention obligations for review; transfer and continuity depend on the agreed scope.
Adopt in stages with a shared plan.
Review the first workflow, stakeholders and trust evidence together before expanding.
Start as a layer
Migration does not have to mean instant rip-and-replace. Buyers can phase Sentus around the pressure point hurting first, then expand into the broader platform.
Stakeholder-safe rollout
Operations, ownership, procurement, and implementation teams should all see the same written plan before cutover decisions get made.
Trust and rollout stay connected
Migration only feels safe when trust evidence, rollback posture, and implementation sequencing are all visible in the same buyer path.