A self-storage software migration is a change to an operating system in the literal sense: it affects how your team collects rent, admits tenants, answers questions and closes the day. A polished demonstration is useful, but it cannot tell you whether a particular balance, access code or payment agreement will arrive correctly. Evaluate the transition as carefully as the new interface.
Start with a written migration workbook. Give each facility its own row, identify the source of each dataset, and name the person who can approve the result. This guide is an evaluation framework, not a promise about Facily’s migration scope or completion time. Confirm the actual scope with both providers before setting a date.
1. Inventory the records your team actually uses
List active and former tenants, units and unit groups, leases, recurring charges, deposits, credits, open balances, reservations, documents and access permissions. Separate historical records you need inside the new product from records you only need to retain in an accessible archive. Importing everything is not automatically better if the history arrives without useful context.
- Stable identifiers. Preserve source tenant, unit and lease IDs so you can trace an imported record back to its origin.
- Definitions. Write down what occupied, reserved, unrentable and past due mean in each system.
- Export access. Confirm which files, attachments and reports you can obtain, and who is responsible for producing them.
2. Reconcile financial balances before importing
Choose one reconciliation date and export a control report from the current system. For each facility, record occupied units, open receivables, deposits, credits and prepaid amounts. Keep those totals beside the detailed export. A balanced portfolio total can still hide two tenants with offsetting errors, so inspect a sample of individual accounts as well.
Include ordinary and difficult accounts in that sample: an autopay tenant, a recent move-in, a prepaid tenant, a partial payment, a credit balance and a delinquent account. Ask the new provider to show how each one will appear to a manager. Document any transformation instead of accepting a verbal assurance that the numbers are close enough.
3. Treat autopay as a separate migration workstream
An exported tenant list is not proof that saved payment methods can move. Ask the current processor and the receiving provider which payment details can transfer, what permissions and coordination they require, and how recurring payment schedules will be mapped. Stripe’s migration documentation is one example of a provider-specific process; it does not establish what another processor supports.
Get an explicit answer for tenants whose details cannot transfer. Decide who communicates with them, how they securely update their payment method, and how the team confirms that recurring payments are ready. Keep sensitive payment data within the processors’ approved transfer process rather than treating it as another spreadsheet attachment.
4. Test access control and tenant communications
Create an access checklist for gate codes, keypad integrations, facility hours and account-status changes. Confirm which system becomes authoritative after cutover and what happens if the connection is temporarily unavailable. Test a permitted entry and a deliberately restricted test account through an approved operational procedure; a successful dashboard sync alone does not prove that the gate behaves as expected.
Review welcome messages, receipts, payment reminders and rate notices. Make sure old and new systems will not both send the same message. Identify messages that should pause during the transition, and have an accountable person approve when each automation resumes. Avoid changing collection rules during the migration unless that is a separately reviewed project.
5. Run a rehearsal with a written pass/fail checklist
Use an agreed sample or test import before the production cutover. Validate the same reconciliation totals, inspect the exception accounts, test the staff roles and walk through a reservation, move-in, payment correction and move-out. Invite the people who do the work daily; an owner’s high-level review will not catch every front-desk problem.
- Owner. Who corrects a source-file error, who reruns the import, and who approves the result?
- Evidence. Which reports or screenshots demonstrate that each acceptance check passed?
- Fallback. What conditions stop the launch, and what is the agreed recovery procedure?
6. Plan the cutover around the people doing the work
Pick a window that fits your facilities’ operating pattern, not just a software calendar. Define when changes stop in the old system, when the final export happens, and how urgent work is captured during the gap. Give staff a single escalation channel and a concise list of the tasks they must check on the first day.
After launch, repeat the reconciliation and review failed payments, duplicate messages, access exceptions and unresolved account questions. Keep a named owner on the issue list until it closes. A migration is complete when the team can trust the operating records, not merely when the import progress bar reaches the end.
Questions to take into a software demonstration
- What exactly is included? Ask for a field-level scope, supported history, attachment handling and explicit exclusions.
- Can we see a rehearsal? Use your exception cases to evaluate the provider’s approach before agreeing to a launch date.
- How do we leave later? Ask how you can export operating records and what format you will receive.