1. Define the operating model before configuration
Start with how leasing, accounting, maintenance and management work today, then decide what should change. AppFolio configuration should support the target operating model rather than become the operating model by default.
Document process owners, decision points, approvals, exception handling and reporting requirements before the team begins detailed configuration.
- Identify process owners for leasing, accounting, maintenance and resident operations
- Document current workarounds and manual steps
- Define what should be standardized across properties
- List reports and management questions the new setup must support
2. Prepare accounting and data early
Data preparation is usually one of the largest implementation risks. Property, resident, lease, vendor and accounting information needs clear ownership and validation rules before conversion begins.
Accounting design should be treated as an implementation foundation, not a late-stage cleanup task.
- Review chart of accounts and coding conventions
- Identify duplicate or incomplete records
- Define historical-data requirements
- Reconcile source balances before conversion
- Assign validation responsibility to business users
3. Design permissions and workflows around roles
Permissions should reflect actual responsibilities and controls. Overly broad access can weaken controls, while overly restrictive access can create unnecessary handoffs.
Each major workflow should specify who starts the work, who approves it, what information is required and how exceptions are handled.
- Map user roles to responsibilities
- Define approval levels
- Document leasing and maintenance handoffs
- Test exception scenarios, not only happy paths
4. Test with real business scenarios
Testing should use realistic property, resident, vendor and accounting scenarios. A technically successful import is not enough if teams cannot complete the work required after go-live.
Create a test plan that includes reconciliations, operational workflows and management reporting.
- Lease creation and renewal
- Move-in and move-out
- Invoice coding and approval
- Work-order assignment and completion
- Resident balances and accounting reconciliations
- Management and owner reporting
5. Train around the process, not the screen
Training is more effective when users understand what they own, why the workflow exists and what happens next. A list of clicks does not create operational consistency.
Use role-based training and document the standard operating process alongside the system steps.
- Create role-based training
- Use realistic examples
- Document responsibilities and escalation
- Schedule post-launch reinforcement
6. Plan cutover and stabilization
Go-live should include ownership for final conversion, issue triage, communications and decision-making. Expect a stabilization period and define what constitutes a critical issue.
Measure whether the implementation is actually reducing work, improving visibility and supporting the operating model.
- Define cutover timing and freeze windows
- Create an issue-priority system
- Assign decision owners
- Track unresolved data and workflow issues
- Review results after the first operating cycles
Where Real Ops fits
Real Ops supports AppFolio implementations from readiness through stabilization, including data cleanup, accounting design, workflow configuration, testing, training and operational improvement.