Entity Explorer
A functional and semantic description of the data needed for your migration. This is not a rigid technical database schema, but rather a business-oriented view of the information we'll be working with.
14Total Entities
Sort:
Filter:
Associations
associationRequired For Migration
Core information for homeowner associations including identifying data, contact information, and contract terms. Operational configuration (billing, accounting setup, etc.) is managed separately.
18fields
•2relations
“This schema captures core association data for migration purposes.”
Unit Types
unit_typesOptional For Migration
Core information for unit type classifications including identifying data and assessment details. Units can reference types by any unique identifier (ID, name, or composite).
6fields
•2relations
“Unit types define categories like 'Single Family Home', '2BR Condo', 'Townhouse', 'Villa', etc.”
Units
unitRequired For Migration
Core information for individual properties or units within the community. Units are the physical properties (homes, condos, lots) that have accounts and are associated with owners/tenants.
9fields
•3relations
“Each unit belongs to exactly one association/community”
Accounts
accountRequired For Migration
Core information for billing accounts for units or properties. Accounts are where charges are applied, payments are received, and balances are tracked. THIS DATA IS REQUIRED for migration.
11fields
•5relations
“THIS DATA IS REQUIRED - Critical for migration success”
Community Members
community_memberRequired For Migration
Core information for people associated with accounts in specific roles. Each member has an account-level role (owner, tenant, or occupant) and optionally one or more association-level roles (board member, CAM). This represents the minimum data needed to identify people and their relationships to billing accounts and the HOA.
16fields
•2relations
“THIS DATA IS REQUIRED - Critical for migration success”
Charge Types
charge_typesRequired For Migration
Charge/assessment type codes that categorize different types of charges billed to homeowners.
6fields
•2relations
“Charge types categorize assessments, fees, and charges billed to homeowners”
Delinquency Statuses
delinquency_statusesRequired For Migration
Delinquency status codes that track collections workflow stages for accounts with overdue balances.
6fields
•1relation
“Delinquency statuses track the collections workflow stage for overdue accounts”
Reimbursables
reimbursablesRequired For Migration
Billable item codes for charges the management company bills back to the Association (postage, copies, professional services, accounting fees, etc.).
7fields
•1relation
“Reimbursables are billable items the management company charges back to the Association (the HOA entity)”
Operating Bank Accounts
operating_bank_accountsRequired For Migration
Core information for association's operating bank accounts including identifying data, routing information, and contact details. Operational configuration (check layout, GL codes, ACH settings, lockbox) is managed separately.
12fields
•1relation
“⚠️ CONTAINS SENSITIVE DATA - Banking information must be properly secured”
Recurring Charges
recurring_chargesRequired For Migration
Core information for recurring assessments or fees applied automatically to accounts based on unit type and schedule. This is how regular HOA dues, maintenance fees, and other periodic charges are defined.
10fields
•2relations
“Each recurring charge applies to all units of a specific type within the association”
Account Addresses
account_addressOptional For Migration
Core information for additional mailing addresses for accounts. Use when correspondence should be sent to an address other than the property address (e.g., owner's home address, property manager's office, power of attorney).
8fields
•2relations
“Use when accounts need correspondence sent to addresses other than the unit address”
Account Notes
account_noteOptional For Migration
Core information for notes and annotations associated with accounts, providing additional context and historical record of account-related information.
6fields
•1relation
“Account notes provide historical context and audit trail for account activities”
Tracked Items
tracked_itemsOptional For Migration
Physical items tracked by the HOA and issued to homeowners, requiring deposits, tracking, or return management (gate remotes, pool passes, parking permits, keys, etc.).
12fields
•2relations
“Tracked items are OPTIONAL - only needed for associations that track physical items issued to homeowners”
Vendors
vendorsOptional For Migration
Core information for service providers and contractors including identifying data and contact information. Operational configuration (payment methods, tax processing, work orders) is managed separately.
12fields
•1relation
“This schema captures core vendor data for migration purposes.”
About this documentation: These entity descriptions represent the business and functional requirements for your data migration. Each entity describes what information we need and why, rather than the exact technical implementation details.