Discovery
Current processes, pain points, reporting needs and scope.
Resources · Guides
Property management software implementation guide
A successful property management software implementation follows six phases: discovery, design, configuration, data migration, testing and go-live, then stabilisation. This guide explains each phase, who is involved, what can go wrong and how to prepare, using RIOO on NetSuite as the worked example.
Implementation guide
- PrepareEntities, charge codes, files
- ConfigureProperties & roles
- MigrateBalances & leases
- TrainBy role
- Go liveHypercare
Why do implementations succeed or fail?
Implementations succeed when ownership is clear, data is ready early, processes are redesigned rather than copied from the old system, and testing uses real scenarios. They fail for the opposite reasons, which is why governance and preparation matter more than software features.
Most implementations that struggle do so for the same reasons: unclear ownership, data that is not ready, processes copied from the old system without question, and too little testing with real scenarios. Software rarely fails on its own. Projects that succeed have an executive sponsor, a decision-maker from finance and operations, clean data, and a short list of real scenarios that must work on day one.
How it works
Which test scenarios matter most?
The test scenarios that matter most cover a new lease with deposit and escalations, a month of billing and payments by every method, late fees and payment plans, a maintenance request with a vendor bill, a renewal with a rent increase, and a move-out with deposit deductions.
- 01
Create a new lease with deposit, escalations and recurring charges.
- 02
Bill a month and apply payments by each method you accept.
- 03
Run a late fee and a payment plan.
- 04
Raise a maintenance request, assign a vendor and post the bill.
- 05
Process a renewal with a rent increase.
- 06
Complete a move-out with deposit deductions.
- 07
Close the month and produce property and owner reports.
How it works
What are the phases of an implementation?
An implementation runs in six phases: discovery of the portfolio and scope, design of how properties, charges and roles map to the system, configuration in sandbox, data migration with control totals, scenario and parallel testing, then go-live at a period end and stabilisation through the first close.
- 01
Discovery
Understand the portfolio, entities, processes, integrations and pain points. Output: scope, success measures and a plan.
- 02
Design
Decide how properties, entities, charges, accounts, roles and workflows map to the system. Output: a design document signed off by finance and operations.
- 03
Configuration
Set up the property hierarchy, charge codes, templates, approval workflows, portals and integrations in a sandbox.
- 04
Data migration
Extract, clean, map and load units, leases, tenants, balances, deposits and open work, with control totals. See the data migration guide.
- 05
Testing
Run scenario tests, then a full parallel cycle of billing, collections, maintenance and close.
- 06
Go-live and stabilisation
Cut over at a period end, support users closely through the first close, then optimise.
Use cases
What does a project plan typically include?
A project plan typically includes discovery, design of segments, charge codes, workflows and roles, configuration in sandbox, data migration in test cycles, scenario and parallel testing, role-based training with your own data, and go-live with support through the first close.
Design
Segments, charge codes, workflows, roles and integrations.
Configuration
Building the design in a sandbox.
Data migration
Extracting, cleaning, mapping and loading data in test cycles. See the data migration guide.
Testing
Scenario, user acceptance and parallel testing.
Training
Role-based training using your own data.
Go-live and hypercare
Cutover, first month-end and stabilisation support.
Checklist
What are the warning signs of a struggling project?
Warning signs of a struggling project include decisions open for more than two weeks, data cleansing left until just before go-live, users first seeing the system at training, testing with invented data, no agreed definition of success, and integrations scoped late in the project.
- Decisions open for more than two weeks.
- Data cleansing left until just before go-live.
- Users first seeing the system at training.
- Testing using invented data instead of your own leases.
- No agreed definition of success for go-live.
- Integrations scoped late.
How should you test?
Test with scenarios, not menus. Work through real situations end to end, such as a new lease with a deposit and concession, a mid-lease rent change, partial and returned payments, and a maintenance request with a vendor bill, then compare results with your expected figures.
Test with scenarios, not menus. A good scenario set includes a new lease with a deposit and a concession, a mid-lease rent change, a partial payment and a returned payment, a maintenance request with a vendor bill and a chargeback, a move-out with deductions, and a month-end close with an intercompany fee. Then run one full cycle in parallel with the old system and compare totals: rent billed, cash received, receivables, deposits and expenses.
Compare
What does go-live look like?
Go-live follows a short sequence: freeze new transactions in the old system at period end, run the final data extract and load, tie out balances before the first billing run, and switch payment flows and the tenant portal before the next rent due date.
| Step | Timing |
|---|---|
| Freeze old system for new transactions | Period end |
| Final data extract and load | First days of new period |
| Tie out balances | Before first billing |
| Switch payment flows and portal | Before rent due date |
| Communicate to residents and tenants | Several weeks ahead, then at go-live |
| Daily stand-ups and issue log | First weeks |
| First close review | End of first period |
How do you drive adoption after go-live?
Train by role, using the team's own properties and scenarios. Name champions in each region. Retire old spreadsheets and access deliberately, so there is one place to work. Track a few measures, such as time to close, collections rate and work-order response, and share progress. RIOO's customer experience team supports this phase.
Compare
How long does a property management implementation take?
Duration depends on the number of properties, entities and markets, the quality of source data, integrations and how much change the team can absorb at once. Small single-entity portfolios can move quickly; multi-entity, multi-market groups usually phase go-lives by portfolio so each wave builds on proven templates.
| Factor | Shortens the project | Lengthens the project |
|---|---|---|
| Data quality | Clean, current lease data | Gaps, duplicates, paper leases |
| Scope | Core leasing and accounting first | Every module at once |
| Entities | One or few subsidiaries | Many entities and currencies |
| Integrations | Standard connectors | Custom integrations |
| Decision-making | Empowered project owner | Decisions by committee |
In detail
What should you prepare before kick-off?
Before kick-off, prepare a portfolio list with legal entities, every charge code mapped to GL accounts, current lease templates and notices by jurisdiction, a list of integrations, five to ten real scenarios written step by step, and named owners for each data set.
A portfolio list
Properties, buildings, units and their legal entities.
Charge codes and accounts
Every recurring and one-off charge, mapped to GL accounts.
Lease templates and notices
Current documents by jurisdiction.
Integration list
Payments, screening, messaging, listings, utilities and any data feeds.
Five to ten scenarios
Real situations the system must handle, written step by step.
Data owners
Named people for each data set who will clean and sign off.
Compare
Who needs to be involved?
An implementation needs an executive sponsor to set priorities and remove blockers, a project lead to run the plan, a finance lead to own charges, accounts and balance sign-off, an operations lead for leasing and maintenance processes, and an IT or NetSuite administrator.
| Role | Responsibility |
|---|---|
| Executive sponsor | Priorities, decisions, removing blockers |
| Project lead | Plan, risks, communication |
| Finance lead | Chart of accounts, charges, close, sign-off of balances |
| Operations lead | Leasing, maintenance and resident processes |
| NetSuite administrator | Roles, customisations, integrations, sandbox |
| Property managers (champions) | Scenario testing, training peers |
| Vendor implementation team | Configuration, migration, guidance |
What should training look like?
Training works best by role and with your own data: leasing agents practise applications and leases, property managers run collections and renewals, maintenance staff close work orders on mobile and finance runs a close. Short recorded sessions and quick reference guides help new staff after go-live.
Who should NOT start an implementation yet?
Pause if no one can own the project day to day, if your ERP decision is still open, or if a major portfolio change such as an acquisition or disposal is imminent. Starting in those conditions usually means redesigning midway.
How does a RIOO implementation on NetSuite differ?
A RIOO implementation differs because RIOO runs in your NetSuite account, so your chart of accounts, subsidiaries, roles and banking are reused rather than rebuilt. Discovery also reviews existing customisations on customer and invoice records, so they work correctly alongside property transactions.
Because RIOO runs in your NetSuite account, your chart of accounts, subsidiaries, roles and banking are reused rather than rebuilt. Discovery includes a review of existing NetSuite customisations that touch customers and invoices. Configuration happens in a NetSuite sandbox first. Existing NetSuite customers often move fastest. See NetSuite implementation and for existing NetSuite customers. Further reading: NetSuite property management implementation and NetSuite real estate ERP implementation guide.
How do you measure whether an implementation succeeded?
Agree success measures before the project starts and measure them at three and six months: days to close the month, time spent on reconciliations, share of payments made online, maintenance speed of response, and user adoption by role. Comparing these with a baseline from the old system shows whether the change delivered what it promised.
Talk to a specialist
See implementation guide on your own portfolio.
This guide explains each phase, who is involved, what can go wrong and how to prepare, using RIOO on NetSuite as the worked example.
How long does a property management software implementation take?
Implementation time depends on portfolio size, number of entities, data quality and integrations. Single-entity residential portfolios move faster than multi-country commercial ones, and a phased rollout by entity or region reduces risk. Ask for a plan built from your own data after discovery rather than a generic estimate. Confirmtypical RIOO timelines
What is the biggest risk in an implementation?
Data quality is the biggest risk. Duplicate tenants, wrong opening balances, missing deposits and incomplete lease terms cause most post-go-live problems. Start cleaning data early, assign a named owner to each data set, and tie every test and final load to control totals that finance signs off before cutover.
Should we run the old and new systems in parallel?
Yes, for at least one billing and collection cycle. Running both systems and comparing totals for charges, receipts, balances and reports catches configuration and data errors before tenants or owners see them. A parallel month for one representative portfolio is often enough to prove the setup.
When is the best time to go live?
Go live at a period end, after the final close in the old system and before the next rent due date, so opening balances are clean and the first close is a full month. Avoid peak periods such as academic-year turnover for student housing or year-end audits.
Do we need a NetSuite partner to implement RIOO?
Not necessarily. RIOO's team implements the property application, while your NetSuite partner or internal administrator can support wider NetSuite changes such as financial configuration, other SuiteApps or reporting. Responsibilities for configuration, data migration and testing are agreed up front so nothing falls between teams. Confirmservices model
Should we go live at month-end or mid-month?
Most teams go live at the start of a period, so opening balances come from a closed month in the old system and the first close on RIOO covers a full month. Mid-month cutovers are possible but need prorated balances and more reconciliation, which adds risk.
Do we need to run systems in parallel?
Yes, at least for one portfolio. A parallel month, running billing, collections and reporting in both systems and comparing totals, is a good way to prove the configuration and data before switching off the old system. Differences are investigated and fixed before the full cutover.
How much time will our team need to commit?
Expect regular time from finance, operations and IT leads through design, data cleansing and testing, because they make decisions and sign off balances. Users then need time for role-based training and practice with your own data before go-live. Plan backfill for key people during peak weeks. Confirmtypical customer effort
Who should be the project owner?
The project owner should be someone who knows the portfolio and has authority to make day-to-day decisions, typically a finance or operations manager. Protect their time from regular duties, give them an executive sponsor for escalations, and make them accountable for decisions, scope and go-live readiness.
What is hypercare?
Hypercare is a period of extra support after go-live, usually through the first month-end close, when the implementation team stays closely involved, issues are prioritised and fixed quickly, and users get help in real time. Once the first close balances, the account moves to normal support.
Can we change scope during the project?
Yes, through a change log that records each request, its impact on timeline and effort, and the decision. Additions are usually moved to a later phase unless they are needed to go live, which protects the go-live date while keeping good ideas for the next phase.
Related
Related to implementation guide
