Instead of Urbanise Strata
Moving off Urbanise Strata? Own the strata system your managers live in.
Enterprise DNA builds your firm its own strata system around how your team runs meetings, chases levies and keeps the registers. We bring your Urbanise plans, owners and levy positions across and run it for you, with the trust ledger left in an accounting system built for it.
Urbanise publishes no price for Urbanise Strata. Its own FAQ says it is costed per lot, with volume discounts, and you get a figure through a demo and a proposal.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
What the subscription covers
Paying per lot for a view of your own plans
Your plans, owners, entitlements and meeting history are the firm's records. Urbanise prices access to them by the lot, and the figure only arrives in a proposal.
Costed per lot, in their own words
Urbanise's FAQ says Urbanise Strata is costed on a per-lot basis and that as your business grows, the software cost grows along with it. Every new plan you win lifts the subscription.
No price until the proposal
There is no pricing page. You book a demo, confirm training and migration needs, then receive a proposal to sign. Volume discounts apply.
A cost your owners may end up carrying
The platform is built so managers can pass the software cost on to their owners corporations or absorb it into management fees. Either way somebody pays it on every lot.
Migration and training as a project
The proposal sets out a project timetable, data migration and a training programme before kick-off. Static data goes in through Urbanise's Excel templates; aged levy balances and the balance sheet are typically keyed in by hand.
Partners behind key features
Meetings run on a module powered by StrataVote, and the help Urbanise promotes for turning your data into action comes through a partner, Merlo AI,.
Data in through templates, silence on the way out
Urbanise explains in detail how data comes into the platform from your old system. Its strata page says nothing about how a firm takes its plans, owners and history back out.
What you run instead
A strata office that answers when asked
Arrears
Overdue levies, step by step, across the portfolio
Every levy run is split across the lots by entitlement. Lots that fall behind move through your firm's own recovery steps, each one dated, so the file is complete when it goes to a collector.
- check One question lists every lot behind on levies, oldest debt first, with the next step named
- check A lot that skipped the reminder or the formal demand shows up before recovery starts
- check The letter for that step drafted from the ledger for a manager to check and send
- check Which plans and which owners fall behind again and again, answered across every manager's book
Meetings
General meetings held inside the legal window
Each plan's annual meeting is tracked against the deadline its law sets, with the notice period counted, so a short-notice meeting is caught before the resolutions are open to challenge.
- check Every plan shown as held, booked or at risk, worst first
- check The agenda built from the plan's own year: levies to set, a valuation due, works above the committee's limit
- check Meeting notices in your firm's colours, without a separate meetings module
- check Minutes followed until they have reached the owners
Registers
Insurance, sale disclosures and compliance you can question
The registers a manager checks plan by plan become records you can ask about for the whole portfolio, each rule pointing to the law it comes from.
- check Every policy with its expiry, premium and the age of the valuation behind the sum insured
- check A sum insured below the latest valuation called out on the day the valuation is recorded
- check Sale disclosure requests tracked against the clock, oldest first, with the conveyancer named
- check One compliance run across the rules your plans live under, with the source of each rule shown
Ownership
Your records, your documents, your rules
Plain records in a database your firm controls, documents in your own brand, and no figure on the invoice that rises with your lot count.
- check Levy notices, arrears letters and meeting notices rendered in your firm's branding
- check Read-only pages for the week and the portfolio, opened in any browser
- check New fields, rules and reports added by describing them in plain English
- check Open source with no licence fee: the records stay yours if you ever stop working with us
Make it yours
Design your own Urbanise Strata replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Urbanise Strata. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Urbanise Strata data across and run it for you.
Switching
How to switch from Urbanise Strata
The move is a staged export, test import and record check, with a separate plan for trust accounting before you stop using Urbanise.
- 1
Request your Urbanise exports
Ask Urbanise how to export what your account allows, usually as CSV or Excel, and check the available options with them. Request spreadsheet exports of your plans, lots, entitlements, owners, insurance and aged levy balances. These are the records the move needs to start with. Keep the exported records available so you can compare them with the test import.
- 2
Load a test import
Load the records as a test import before keeping anything. Urbanise's columns will not match the replacement's standard import, so the data needs to be mapped into the right fields. You can ask Claude Code to map them, or have Enterprise DNA handle the mapping when they run your version. Agree on the opening balance for the levy record.
- 3
Review what the import flags
Check the test import's results before accepting the records. Review anything it flags, confirm that the plans, lots, owners, insurance and levy balances have landed as expected, and resolve fields that did not map cleanly. Decide which records to correct, map differently or leave out. Do not treat the import as complete until you are satisfied with the records and the agreed opening levy balance.
- 4
Run both systems together
Keep Urbanise running while you use the new database alongside it for a short period. Check that your managers can find the records and follow the work they handle, including arrears steps, meetings and maintenance. Compare the new records with Urbanise as you go, and correct any remaining differences before you depend on the new system for day-to-day work.
- 5
Switch off Urbanise
Stop using Urbanise only after you have checked the move and decided where trust accounting and banking will live. Body Corporate for Claude Code does not receipt money, pay contractors or reconcile a trust account. Keep that work in a separate accounting system. If you use the free version, do not switch off the system that currently holds your trust accounting until you have a suitable replacement in place.
Where the real effort goes
Most of the work is mapping Urbanise's columns to the replacement's fields, matching your firm's rules, and deciding how much history to bring across. Financial data such as aged levy balances needs careful handling, and the levy record starts at an agreed opening balance. If you have Enterprise DNA run your version, they handle the mapping and the move off Urbanise.
Not ready for a call?
Get your Urbanise Strata switch plan by email
We will send you the step-by-step plan for moving your business off Urbanise Strata, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Urbanise Strata switch plan is on its way.
Rather talk it through? Book a call arrow_forwardChoose your route
Try the free version, or have Enterprise DNA build and run yours
Open source
Run it yourself
Free
- 1 Download the free version from GitHub
- 2 Load the demo plans and open the folder in Claude Code
- 3 Ask which lots are behind and which meetings are at risk
- 4 Ask Claude Code to map the spreadsheets you export from Urbanise, with a test import first
Omni by Enterprise DNA
Have Enterprise DNA build it for you
One setup fee, then a monthly retainer
- check We bring your Urbanise plans, lots, entitlements, owners and levy positions across and check them against your old reports
- check The rules for each state or country you manage in, your notice periods and your recovery steps written in
- check An owner-facing page or a link to the accounting system that holds your trust ledger, if you want one
- check Run for you inside Omni, our managed Command Center, alongside the rest of your business
Questions
Instead of Urbanise Strata, answered
Urbanise does our trust accounting and banking. What happens to that? expand_more
That part needs a home of its own. The free version keeps a levy record so arrears add up, but it never receipts money, pays a contractor or reconciles a trust account, by design. Trust accounting is audited and regulated, so it belongs in an accounting system built for that job. When we build your version, we connect it to whichever trust accounting system you choose, and everything around the money moves across: plans, owners, meetings, arrears steps, maintenance, insurance, disclosures and compliance.
Our owners use the Community portal and app. Do they lose that? expand_more
Not unless you decide it is not worth keeping. The free version gives owners what they rely on most: correct levy notices, proper meeting notices and minutes that arrive. If your owners expect to log in, Enterprise DNA can build an owner page into your version, drawn from the same records, in your firm's branding rather than a software vendor's.
How do we get our data out of Urbanise? expand_more
Urbanise's strata page describes how data comes in, not how it goes out, so ask them for spreadsheet exports of your plans, lots, entitlements, owners, insurance and aged levy balances. Their columns will not match the free version's standard import, so mapping them is part of what Enterprise DNA does, or you can ask Claude Code to map them. Either way there is a test import before anything is kept, and the levy record starts at an agreed opening balance.
We manage plans in more than one state. Do the rules fit? expand_more
The free version's rules cite New Zealand's Unit Titles Act 2010, with the New South Wales and Queensland strata Acts mapped at a high level in the same rule book. The rules are records you change in plain English: meeting deadlines, notice periods, recovery steps. When we build your version, we write in the rules for every state you manage in. It checks your records against your rule book; it is not legal advice.
Can a strata firm with no developers really run this? expand_more
Yes, if Enterprise DNA builds and runs it. Your managers ask plain questions, such as which levies are sixty days behind or which meetings fall due next quarter, and get answers from your records. We handle the setup, the move off Urbanise and the upkeep. The free version suits a firm with someone who is happy to run it themselves.
Win the next building without adding to the software bill
30 minutes with Sam. Bring your Urbanise proposal or latest invoice and your lot count. We look at what your managers use each week and what your own version would look like. If it fits, we build it. If not, the free version is yours to run.
Body Corporate for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Urbanise Strata?
Get your version built