In this article
A transition succeeds when the next team can act on unfinished work. Moving records is only one part of transferring responsibility.
Choose the boundary of the transition
A staff coverage change, a new management assignment and a software migration have different authority, privacy and technical requirements. This article offers a role-level planning method, not instructions to export a live database or change account access. Use the relevant agreements, authorized administrators and professional guidance for the actual transition.
AppFolio’s public contact page gives managers a product-support route. Ask account-specific questions there rather than assuming a public feature description establishes what data can be transferred or how a migration should be performed. No private account or export format was tested for this atlas.
Inventory open loops before files
Start with work that still needs an action: an application awaiting authorized review, an unaccepted maintenance assignment, a resident question awaiting a reply, or a record discrepancy awaiting verification. Capture the current state and the receiving role in the approved internal record.
For each loop, distinguish responsibility for doing the work from responsibility for checking it was received. A departing role should not merely send a large archive and assume the transfer is complete. The receiver needs a practical way to identify priority, prerequisites and exceptions.
Fictional coverage change
A coordinator will be absent for a week. Instead of forwarding the whole inbox, the team reviews open scheduling questions, identifies the accepted backup role and checks that the backup can access the necessary authorized records. Unrelated resident information is not copied into a new personal document.
Test comprehension and access separately
A receiver may understand the task but lack appropriate access, or have access without understanding the next action. Test both conditions through authorized procedures. Do not share passwords or one-time codes as a shortcut. Persistent access changes belong with the responsible administrator and applicable approvals.
- Comprehension: the receiver can state the next action.
- Evidence: the relevant source record is identifiable.
- Access: the receiver has the authorized capability needed.
- Exception route: unresolved gaps have a decision owner.
Confirm the transfer without erasing the trail
A transfer receipt should say which responsibilities were accepted and which remain unresolved. Keep a permitted history of the change so a later question does not restart from memory. Retention and deletion decisions are separate from operational handoff and should follow the organization’s actual requirements, not a generic checklist.
When a system is changing, agree on the source of truth during the overlap and who can authorize corrections. Otherwise, both systems may accumulate different versions of the same task. A controlled pilot can reveal mismatched definitions before a broader authorized transfer, but this publication cannot specify a migration plan for an unseen environment.
Use the change-trail method and the local handoff planner to prepare questions. The planner transfers nothing, grants no access and makes no promise that a transition is complete.
Source notes and boundaries
Public sources checked October 21, 2026. The process methods and fictional examples are original editorial guidance, not AppFolio instructions or a test of a private account. Features, labels and permissions can vary.
- AppFolio: contact and support routes — Different official support routes for property managers, residents, property owners and investment-management users.