A preview before anything changes
The first run is a dry run. It shows header problems with did-you-mean suggestions, and a plan for every row: whether it creates or updates a household, the role it infers and the reason. Rows with a problem are listed with the cause, such as a missing parcel number, a missing address, an invalid email or phone, or a parcel conflict. Nothing is saved until you apply.
One household per parcel
Each parcel becomes a household, and a multi-unit parcel becomes one household per unit. The primary and secondary contacts become residents in an Imported status, and no invitation is sent during the import, so you invite people when you are ready. Meters, owner and account number are kept on the household. Owner, renter or landlord is inferred and can be edited.
Upload GeoJSON or KML, or draw each boundary by hand.
Placed in a neighborhood, ready for the app
Imported residents are placed in neighborhoods from their addresses, so alerts and challenges work from the first day. Water and electric meters become service accounts for payments only when that option is turned on with City Payments. A file can hold up to 2,000 rows.
Common questions
Bloomz staff run the import with your clerk during onboarding. Your clerk reviews the preview and approves the apply.
No. Contacts are imported with no invitation. You invite residents when you are ready.
A spreadsheet export with a parcel number and a service address. Meters, owner and contacts make it richer.
No. The address already on record is kept.
More of Bloomz for Cities
See Bloomz
in your city.
A short call focused on your city's size, your priorities and the systems you use today, not a generic pitch.
