How to prepare rental data before changing systems

Changing tools does not automatically repair a disorganised spreadsheet. If two rows represent the same property or one column mixes rent with comments, the problem can travel into the new system. Useful preparation means defining what each row represents, retaining an original copy and checking a sample. This approach works whether you enter records manually or use an import process supported by your destination tool.

Preserve the original file

Create a dated working copy instead of cleaning the only existing file. Note which sheets contain properties, people, agreements or payments. Inspect filters and hidden rows before counting records. Microsoft's guidance recommends placing similar data in the same column and using clear headings. Apply that principle to your situation without deleting observations you still need to interpret or move elsewhere. Record who owns the working copy so colleagues know where to send corrections.

Define the unit represented by each row

One row per property and one row per rental month answer different questions. Do not mix them in a table without identifying the record type. Use stable references to connect a property with its payments or agreements. In a hypothetical example, January, February and March rows are not three different properties. Deduplicating solely by address could remove the history you meant to preserve. Review apparent duplicates before deciding what should be merged or removed.

Review formats and unresolved values

Check ambiguous dates, decimal separators and spaces in identifiers. Distinguish zero rent from unknown rent. Do not invent a date simply to make an empty field disappear. Prepare a short dictionary explaining each column, its permitted values and the meaning of missing information. That document lets another person review the transfer without relying entirely on whoever created the spreadsheet years ago. Keep unresolved cases in an explicit list with an owner.

Test a representative sample

Choose straightforward cases and potentially difficult ones: two units in one building, a tenant change or a partial payment. Transfer this sample through the process the destination actually supports. Check counts, amounts and relationships, not merely whether rows appear on screen. Do not assume Rentcla or any other tool accepts a particular format before checking its available workflow and fields. A small verified sample is more useful than quickly moving a large dataset you cannot reconcile.

Close the change with a practical check

Agree which file stops receiving edits, who records later changes and how exceptions will be resolved. Retain the original for authorised reference during the transition. The work ends when someone else can locate a property and verify its information, not when a progress bar finishes. Once the data is consistent, Rentcla's property grid is easier to maintain and less dependent on improvised corrections. Schedule a follow-up review to catch issues that appear during ordinary use.

Source: Microsoft guidelines for organising data in Excel.

Read next: How to record partial rent payments without losing the balance.