How to Switch Commercial Property Management Software Without Missing Lease Dates
Changing property management software can feel like an administrative project until a date gets lost. A renewal option notice period, rent escalation, insurance expiration, CAM true-up deadline, or lease end date may be sitting in a spreadsheet, an inbox, a calendar, a lease abstract, and the current system at the same time. Moving the record is not the same as proving which version controls.
The goal of a transition is not to copy every field as quickly as possible. It is to give the next person who opens a lease record a clear answer to three questions: What is the date or amount? Where did it come from? Who verified it?
Use this workflow to organize a software switch around the records that affect billing, notices, and tenant communication. It is operational guidance, not legal, tax, or accounting advice. The executed lease, amendments, and applicable requirements control; have qualified counsel or advisers interpret unclear lease language or confirm compliance decisions.
1. Inventory the dates that can create a real problem
Start with dates that create a decision, a notice, an invoice, or a tenant expectation. Do not begin with the fields that happen to be easiest to export.
For each active lease, build a transition inventory that includes, where applicable:
- Lease commencement, possession, rent commencement, and expiration dates.
- Renewal, extension, termination, purchase, or other option deadlines, including notice windows.
- Base-rent escalation dates, amounts, formulas, and any supporting schedules.
- Free-rent periods, abatements, and billing start or stop dates.
- CAM, tax, insurance, utilities, and other additional-rent billing schedules.
- Certificate-of-insurance expirations, guaranty dates, and required follow-up dates.
- Dates in pending amendments, assignments, defaults, or negotiated changes that are not yet reflected in the current rent roll.
Put the property, suite, tenant, lease name, date type, current value, source document, and status in the same working inventory. A simple table is enough at this stage. What matters is that you can see what must be carried forward and what still needs review.
If your leases were never abstracted consistently, use a structured review before the move. Our Commercial Lease Abstract Checklist for Landlords walks through the provisions and source documents worth collecting into one working record.
2. Give the transition one data owner
Software vendors can help load data, but they should not become the final authority on a lease date. Name one internal data owner for the transition. That person does not need to interpret every provision alone. They do need the authority to identify a conflict, route it to the right reviewer, and record the final decision.
Define the roles before data starts moving:
- Data owner: maintains the master transition inventory and decides when a field has enough support to load.
- Lease reviewer: compares dates, obligations, and amendments against the executed file; escalate ambiguous interpretation to qualified counsel.
- Accounting reviewer: checks amounts, recurring charges, credits, and opening balances against the agreed cutover records.
- Operations reviewer: confirms alerts, tasks, tenant contacts, and notice workflows are usable after the move.
- System contact: documents how the new system represents each field, import exception, and unresolved item.
This prevents the most common handoff failure: everyone assumes someone else checked the date. The owner should also maintain an exception list for records that are incomplete, disputed, or awaiting professional review. Do not hide those records just to reach a migration percentage.
3. Map every field back to a source record
Before importing, make a field map for the critical information. For each destination field, record the source file, source location, old-system value, new-system value, and any transformation made during the move.
For example, an option deadline may appear in a lease body, an amendment, and a manually created calendar reminder. The new record should preserve the original date and a link or reference to the controlling executed document—not simply inherit the calendar reminder without review.
Keep the mapping especially clear for:
- Dates calculated from another event, such as an option notice deadline stated as a number of months before expiration.
- Escalations based on a schedule, percentage, index, or anniversary date.
- Charges that are stored as a monthly amount in one system and an annual amount in another.
- Tenant-specific exceptions, caps, exclusions, and amendment changes.
- Open credits, unapplied cash, delinquencies, and upcoming invoices around the cutover date.
This is also the right time to separate facts from assumptions. A record can say, “Expiration date entered from executed lease, page 14,” or “Escalation amount pending review of Amendment No. 2.” Both are more useful than a clean-looking field with no history.
4. Test a representative sample before the full migration
Do not discover how a date field behaves after every lease is loaded. Choose a small sample that reflects the work your team actually manages:
- A straightforward active lease with recurring base rent.
- A lease with an upcoming renewal or termination notice window.
- A lease with an amendment that changed a key date or amount.
- A lease with an escalation schedule or free-rent period.
- A tenant with CAM, tax, insurance, or other additional-rent activity.
- A lease with a current balance, credit, or collection follow-up.
Load the sample, then have the reviewers work from the new system as if it were live. Can they find the source record? Can they see the alert date, not just the expiration date? Can they tell whether a change came from an amendment? Can accounting reproduce the next expected charge from the lease record and support?
For a practical way to make that test less theoretical, see Test Commercial Property Software on One Ugly Workflow. The point is not to find a perfect lease. It is to test the one that exposes the real handoffs your team cannot afford to lose.
5. Reconcile dates and amounts at cutover
After the sample works, reconcile the full migration in two passes. First, compare the record counts: properties, suites, tenants, active leases, amendments, contacts, recurring charges, balances, and critical-date entries. A count mismatch is a reason to stop and investigate, not something to clean up later.
Second, compare the information that drives the next 30, 60, and 90 days of work. Review upcoming option notices, renewals, expirations, rent changes, insurance follow-ups, CAM tasks, invoices, credits, and tenant balances. For each exception, note whether the old record, new record, or executed source document controls.
When a date does not match, do not choose the value that is most convenient for the go-live schedule. Pull the source file, identify the version being used, and record the resolution. If the issue turns on lease interpretation, use qualified legal or other professional review rather than treating the migration team as the final decision-maker.
Option dates deserve their own pass because the date people remember is often not the date that matters. A lease may expire in December while the tenant’s option notice is due months earlier. Our Commercial Lease Option Tracking guide explains why the notice window, delivery method, and evidence of notice need to be tracked alongside the headline expiration date.
6. Keep the originals and the decision trail
The new system should make work easier, but it should not become the only place the evidence exists. Retain the original executed lease package, amendments, exhibits, notices, prior abstracts, rent schedules, and cutover exports in an organized location with controlled access.
For each material correction made during migration, keep a short decision trail: the field changed, the old value, the new value, the source reviewed, the reviewer, and the date of the decision. That record helps the team answer a tenant question months later without reconstructing the entire migration from email.
Avoid replacing original documents with renamed or retyped copies when the original is available. A clean abstract is useful; it is not a substitute for the executed record when questions arise.
7. Run both systems long enough to verify the work
A cutover does not have to be a single overnight event. Where practical, use a parallel-run verification period before fully retiring the prior process. During that period, compare the upcoming work generated by each system or workflow: critical dates, charges, balances, task lists, and tenant notices.
Choose a defined period and clear exit criteria. For example, the transition team may require all upcoming critical dates within a selected window to match the verified inventory, all material billing differences to be explained, and all open exceptions to have an owner and due date. The right duration depends on the portfolio, lease complexity, billing cycle, and team capacity.
Parallel verification is not duplicate work for its own sake. It is the time to catch a missing amendment, a monthly-versus-annual amount error, or a notice deadline that was stored as an expiration date before it becomes a tenant-facing problem.
A safer software switch starts with evidence
The strongest migration plan is not the one with the fastest import. It is the one that keeps lease-critical dates connected to their source documents, gives exceptions an owner, and gives the team time to verify what will happen next.
When the next escalation, renewal notice, or CAM charge is visible with its supporting record, the new system has done something useful: it has made the work easier to review instead of easier to overlook.