In this article
A neatly formatted spreadsheet can still contain an unclear relationship. Before migrating records, make sure people can explain which property, unit, lease and owner each row belongs to.
This is a preparation checklist for an authorized onboarding team. It is not a replacement import template, a migration service or advice to upload records to this website. Keep source files and private data in the organization’s approved environment.
Begin with the current official template
Buildium publishes onboarding templates and describes uploading them within the customer’s Buildium account in coordination with an implementation specialist. Use the current instructions supplied for the actual onboarding engagement. A spreadsheet saved from another company’s migration may have the wrong structure or assumptions.
Record who supplied the template, when it was obtained and which type of data it covers. Preserve an unchanged copy before mapping your data into it. If a field is ambiguous, ask the implementation contact what is expected instead of putting a plausible answer into a required column.
Create a source inventory before editing
List the source systems and files that contribute records. Identify the intended cutoff date and the person responsible for each source. Distinguish an authoritative record from a working copy or personal contact list. If two sources disagree, mark the conflict for resolution rather than allowing whichever file is imported last to decide the answer.
A useful inventory includes the source name, record type, export date, responsible person and known gaps. It need not reproduce personal details. The purpose is to know where an answer came from and who can verify it.
Build a crosswalk for relationships
Use stable internal references to connect entities across sources. A street address may be written several ways; a person may appear under both an individual and business name; a unit label may be reused at different properties. Normalize presentation only after establishing that the records refer to the same entity.
One source says “Maple 2” and another says “Maple, Unit 02.” The team confirms they refer to the same unit before mapping them to one destination. Two similar owner names, however, remain separate until the authorized record owner verifies the relationship. Similar text alone is not a merge rule.
Keep unknowns visible
Do not substitute zero, an invented date or a generic email address merely to make a file look complete. Ask how the specific import handles an unknown or inapplicable value. A blank with a documented question may be safer to resolve than a confident-looking value that is not true.
Track each exception with the source reference, the unresolved question and the responsible person. Keep the original source unchanged while preparing a controlled working copy. If a correction is agreed, record why and where the authoritative change was made.
Validate a small set of meaningful relationships
After an authorized import, ask the implementation team which validation steps are appropriate. Review counts and representative relationships, not just whether a completion screen appeared. Confirm that selected properties, units and associated records are connected as intended. An upload receipt is evidence of submission, not proof of complete migration.
Buildium’s migration page describes assistance with several record types, but it cannot confirm your particular dataset. Keep the scope and acceptance criteria tied to the actual engagement. Use a versioned handoff index for files and an exception log for unanswered mapping questions. The first monthly review should know which onboarding issues remain open.
Sources and scope
Public sources checked October 21, 2026. The review method and fictional examples are original editorial guidance, not Buildium instructions or accounting, legal or tax advice. No private account was inspected.
- Buildium: Onboarding Templates
Official rental and vendor templates and the account-based upload route coordinated with an implementation specialist. Access: direct public page.
- Buildium: Onboarding and Data Migration
Public description of migration assistance for property, unit, lease, owner, resident and vendor records. Access: direct public page.