“We have no capacity for that right now” — the sentence that extends itself
The most common reason to postpone a migration is workload. The most common reason for that workload is the postponed migration.
7 minute read
Almost every practice weighing up a change of software says the same thing sooner or later: that they are tied up right now, that day-to-day work leaves no room, and that there is simply no capacity to engage properly with a new system. They will come back to it once things calm down.
There is nothing dishonest and nothing unreasonable about that. It is true: a full week leaves nobody two free days. And starting a software migration in that state means working on both at half attention, which puts both at risk.
The problem is not the sentence. It is the date it points at.
"Once things calm down" is not a date
Walk through the management year the way it actually runs:
| Period | What takes the capacity |
|---|---|
| January – March | Previous year's invoices, reconciling accounts |
| March – June | Annual settlements, owner statements, queries |
| April – July | Assembly season, minutes, resolutions |
| July – October | Economic plans, stragglers, buildings taken on |
| October – December | Contracts, notice periods, year-end |
There is no gap in that table. There never was one. "Once things calm down" is not a point in time but a hope, and it is disappointed at the same place every year — not because the practice is badly organised, but because a practice with a growing portfolio looks exactly like this.
Waiting for the quiet week means waiting for something that does not appear in the calendar.
Which work actually takes the capacity
What is telling is which activities fill the day. Rarely the difficult ones. It is the small ones that recur:
- Keeping the same figure in two places — once in the spreadsheet, once in the filing, once in the letter to the advisory board.
- Digging out documents on request and sending them individually by email, often the same document to one owner after another.
- Retyping master data whenever an ownership change comes in or a building is added.
- Entering invoices by hand, line by line, from paperwork that already contains the figures.
- Explaining the same state of play several times over — to an owner on the phone, to the board by email, to a colleague in passing.
None of these is difficult. Each one is small. But together they have two properties that eat the calendar: they grow in step with the portfolio, and they come round again at full cost every year. A growing practice buys this item a second time with every new building.
That is the circle closing: the work that leaves no time for the migration is exactly the work a migration makes smaller.
Tell the duty apart from the habit
Before you migrate anything, one question usually brings the effort down noticeably: how much of what is filling your week do you actually owe anybody?
Part of it: absolutely. The annual settlement and the statement of assets under § 28 WEG, the resolutions register under § 24 (7) WEG, notice periods for assemblies, deadlines towards authorities and insurers. Those duties are fixed and not up for negotiation.
What is not fixed is the manner in which you discharge them. And that is where the overhang sits. Typical examples:
- A list kept alongside the actual record because it has always been kept — and which therefore has to be touched a second time on every change.
- Sending paperwork out individually, when one filing place with access for those entitled answers the same question once and for all.
- Reconstructing historical data that neither a resolution nor an owner has ever asked for.
- Preparing interim figures nobody requested and nobody reads.
In practice, a noticeable share of an overloaded week sits in activities for which, on a closer look, no recipient can be found. That point is independent of any software; it is simply a matter of money.
What you genuinely should not do right now
So that no wrong impression forms — a migration is not an emergency project, and in the middle of a full stretch there are things that would simply be wrong:
- Do not move the whole portfolio now. Migrating the entire portfolio during an already stretched period is exactly the mistake the reluctance in the opening paragraph is right to guard against.
- Do not start booking into a different system mid-financial-year. Half a year in two systems is a settlement nobody can follow, you included.
- Do not make deadline-bound work your test case. Anything with a date on it is the wrong place for a first run.
Anyone telling you to switch completely in the middle of the season is selling you something. The honest roadmap is a different one, and it is here: Going digital in condominium management: the honest roadmap.
What does fit into the gap
Which leaves the question of what is possible instead. The answer is not "nothing" but: the one step that pays for itself inside the same season. There are three candidates, and all three cost hours, not days.
One single building, imported as a dry run. Not productive, not binding — a trial with the data already in your hands. In two hours you learn what you would otherwise learn next year: where your old data has gaps, how long a building actually takes, and whether the import shows you a clean reconciliation before anything is committed. The result is a number you can plan with, instead of a guess.
The invoices already on your desk. Invoice capture does not reach into your bookkeeping — it reads out the supplier, the invoice number, the amount and the date and puts them in front of you to check. Nothing is booked on its own. This is the rare case where the benefit lands immediately, because the pile is already there. What works and what does not is in Invoice capture with AI.
The documents people ask for most often. This is the underrated step. Queries do not arrive evenly across the year, they arrive in a batch — in precisely the weeks when you have the least room to manoeuvre. The declaration of division, the minutes, the insurance policies and the last settlement in one place, visible to owners in their own portal, does not save you work at some point later. It saves it in the same season in which you file it.
Make the busy stretch your measurement
One last suggestion that costs nothing. Over the coming weeks, note two numbers per building: how many hours the work took in total, and how many of those went on searching, retyping and answering the same question again.
At the end you no longer have an opinion, you have an arithmetic. If the total is small, postponing was right, and you can tell any vendor so with a figure. If it is large, you know the amount the next season will cost again — and the decision makes itself.
Either outcome beats the sentence at the top, because that one can be repeated indefinitely and gets a little more expensive each year.
The plan for your own portfolio
If you would rather see the order applied to your own portfolio, you can have it: four questions — how many buildings, what you work with today, where the hours go, when you mean to start — and the plan arrives as a PDF, with the steps in the order those answers call for, and with what you can safely skip.
The gist, in four lines
- The quiet week is not coming. The management year has no gap to wait for.
- The small repetitions are the expensive item, because they are manual duplicate work — and they grow with every building.
- The duty and the manner are two different things. What the law requires is fixed; how you produce it usually is not. The space between the two is worth a look.
- The first step is two hours wide, not two weeks: import one building as a dry run, with the data already in front of you.
What this looks like in Condomana
Migration import
Datenübernahme
Bring an existing portfolio in from a canonical CSV — properties, units, owners, ownership shares, opening balances and historical settlements. Run it as a dry run first, review the reconciliation, then commit. Re-importing never creates duplicates.
Bookings & opening balances
Buchungen & Anfangsbestände
A booking journal per property, with opening balances carried in at cutover — so a settlement stands on real figures from day one.
Invoice capture
Belegerfassung
Drop in an invoice and AI reads out the supplier, the invoice number, the amount and the date for you to check. You correct anything and book it — the AI never books on its own.
Document distribution
Dokumentenverteilung
File every document against the right building and unit, and share it with exactly the owners entitled to see it. Find any file again by full-text search, and every upload is virus-scanned before anyone can download it.
Owner portal
Eigentümerportal
A self-service area, separate from the manager app, where owners see their building’s documents, defects and news, comment, and manage their own profile.
This article explains how we build the software and how the work is usually organised. It is not legal advice. For a decision that turns on your community’s specifics, ask a lawyer or a tax adviser.
Keep reading
Try it on one building
Bring a single property in and see whether it fits. No card, no sales call.