Cloud Property Management Software Kenya: Hosting, Access, Security and the Migration Decision
Cloud property management software Kenya conversations usually skip the question that actually matters and go straight to features, which is how agents end up with a system that does everything they asked for and is unusable on the third Tuesday of the month when the fibre goes down and the whole team is trying to reconcile payments.
The deployment model is a separate decision from the functionality, and it carries its own set of consequences: where your data physically sits and under whose jurisdiction, what happens when your connection fails, who can access your tenant records at the vendor, how quickly you could leave if you needed to, and whether the monthly subscription that looked cheap at forty units still looks reasonable at four hundred.
These are not abstract concerns in this market. Connectivity varies by location and by day, power interruptions take out both the office router and the caretaker’s phone charger, and the Data Protection Act imposes obligations on where and how personal data is handled that most vendors will not raise unless asked.
This guide covers the deployment question specifically: what cloud actually means in practice, how to assess hosting and data residency, how to design for connectivity that is imperfect, what security and uptime commitments to require, how to avoid lock-in, and what cloud property management software Kenya costs over several years rather than one month.
It is written for whoever has to live with the decision, because the functional comparison between products matters less than most buyers assume, and the cloud property management software Kenya deployment choices are the ones that are expensive to reverse — which is why understanding what you are agreeing to when you sign for cloud property management software Kenya is worth the hour it takes.
Table of Contents
- What Cloud Actually Means
- Cloud Versus Desktop Versus Self-Hosted
- Why Most Property Software Moved to Cloud
- What You Give Up
- Where Your Data Physically Sits
- Data Residency and the Legal Position
- Connectivity: The Central Practical Constraint
- Designing for Intermittent Connectivity
- Offline Capability and Sync
- Mobile Access for Field Staff
- Data Consumption and Bundle Cost
- Power Interruption and Access Continuity
- Uptime Commitments and What They Mean
- Security: What to Actually Ask
- Access Control and Internal Permissions
- Encryption in Transit and at Rest
- Backup, Recovery and Restoration Testing
- Vendor Personnel Access to Your Data
- Multi-Tenancy and Data Separation
- Integration and API Access
- Vendor Lock-In and Data Portability
- Exit Planning Before You Enter
- Vendor Viability and Continuity Risk
- Update Cycles and Change Management
- Support Availability and Time Zones
- Migrating From Desktop or Spreadsheets
- Running a Proper Evaluation
- Total Cost Over Several Years
- Data Protection Compliance Obligations
- Contract Terms Worth Negotiating
- Frequently Asked Questions
What Cloud Actually Means {#what-cloud-means}
The term is used loosely, and clarifying it prevents a category of misunderstanding.
Cloud software runs on infrastructure the vendor operates, accessed through a browser or an app, with your data held on their systems rather than on a machine you control.
You are renting access to a service rather than owning a copy of a program, which changes the commercial relationship, the risk profile and the obligations on both sides.
That distinction matters practically. When you stop paying for cloud property management software Kenya, access ends, and whether you retain your data depends entirely on what the contract says, which is not true of a desktop program you bought.
Some vendors describe a hosted desktop application as cloud, which is a different architecture with different characteristics, so establishing what a particular cloud property management software Kenya actually is technically is a reasonable opening question.
Cloud Versus Desktop Versus Self-Hosted {#deployment-models}
Three models exist, and each has a coherent case in the right circumstances.
Desktop software installed on an office machine gives you full control and works without connectivity, at the cost of manual backups, no remote access, and difficulty sharing between users or locations.
Self-hosted software runs on a server you own or rent, giving you control over the data location while requiring technical capacity to maintain, patch and back up, which most property businesses do not have in house.
Cloud removes the maintenance burden and enables access from anywhere, which is why cloud property management software Kenya has become the default, but it makes you dependent on both connectivity and the vendor.
The right choice follows your circumstances rather than fashion. A single-office operation with poor connectivity and a technical person on staff might reasonably choose self-hosted, while a distributed agency with caretakers across the city almost certainly needs cloud property management software Kenya.
Why Most Property Software Moved to Cloud {#why-moved}
The shift happened for reasons that genuinely benefit property businesses, and they are worth naming.
Multi-user access from multiple locations is the first. A property manager in the office, a caretaker at a building and an owner checking a statement all need the same data, which desktop software cannot provide.
Automatic backup is the second, and it addresses the most common catastrophic failure in small property businesses — a failed hard drive with no recent backup, which ends the records.
Automatic updates are the third, so the software improves without anyone installing anything, and a cloud property management software Kenya receives fixes and features continuously rather than in occasional painful upgrades.
Lower entry cost is the fourth. A monthly subscription avoids a large upfront purchase, which suits a growing agency, and a cloud property management software Kenya can be started with a small portfolio and scaled.
Integration with mobile money, messaging and accounting is far easier in a hosted architecture, and a cloud property management software Kenya that receives payment callbacks in real time is doing something a desktop program structurally cannot.
What You Give Up {#what-you-give-up}
The trade-offs are real and should be assessed rather than dismissed.
Control over your data location and handling passes to the vendor, which matters both practically and legally.
Availability depends on your connectivity and their infrastructure, so an outage at either end stops work, and a cloud property management software Kenya user has two dependencies where a desktop user had none.
Cost accumulates indefinitely rather than ending after a purchase, and over five years a subscription frequently exceeds what a licence would have cost.
Switching becomes harder as data accumulates, and a cloud property management software Kenya holding several years of leases, payments and documents is not trivially moved elsewhere.
None of these is a reason to avoid cloud, but each is a reason to negotiate terms and to plan, which is what the rest of this guide addresses for anyone selecting cloud property management software Kenya.
Where Your Data Physically Sits {#data-location}
This is the question most buyers never ask and every vendor should be able to answer.
Data may be hosted in Kenya, elsewhere in Africa, in Europe, in the United States, or spread across regions.
Location affects latency, which affects how fast the system feels. Data hosted far away introduces delay on every interaction, and a cloud property management software Kenya hosted regionally generally feels noticeably faster than one hosted across the world.
Location also affects jurisdiction. Data held in another country is subject to that country’s laws, including whatever access its authorities may have, which is a consideration for records about identifiable Kenyan tenants.
Ask specifically and get the answer in writing. A cloud property management software Kenya vendor who cannot tell you which country your data sits in has not thought about the question, which tells you something about how they have thought about the rest of it.
Data Residency and the Legal Position {#data-residency}
The Data Protection Act imposes obligations on the processing of personal data, including provisions relevant to transferring data outside the country.
Property management data is unambiguously personal data — tenant identities, contact details, payment histories, arrears positions and sometimes employment or guarantor information.
Whether and on what basis you may use a service hosting that data abroad depends on the specifics, and this is a question for a qualified adviser rather than for a vendor’s marketing claim about a cloud property management software Kenya being compliant.
What you should establish factually is where data is hosted, whether local hosting is available, what the vendor’s own compliance position is, and what contractual commitments they will make, so that your adviser can assess the position on real information about the cloud property management software Kenya rather than assumptions.
Some vendors offer a choice of hosting region, which is worth asking about, since a cloud property management software Kenya with a local hosting option removes a category of question entirely.
Registration obligations may apply to you as a data controller, and confirming your own position is separate from confirming the vendor’s.
Connectivity: The Central Practical Constraint {#connectivity}
Connectivity in this market is good in many places and unreliable in others, and it varies by day as well as by location.
An office in Westlands with fibre and a backup line has different constraints from a caretaker at a building in an outer estate on mobile data.
The consequence for cloud property management software Kenya is that the system is unavailable exactly when connectivity fails, which is why a purely cloud-dependent workflow needs a fallback plan.
Assess your actual connectivity honestly rather than optimistically. If your office loses connection for a few hours most weeks, that is a fact to design around rather than an exception, and it should shape which cloud property management software Kenya you choose.
A secondary connection is the standard mitigation. A mobile data backup that takes over when the primary fails costs little and removes most of the exposure, and it should be budgeted as part of adopting a cloud property management software Kenya rather than as a separate concern.
Designing for Intermittent Connectivity {#intermittent-design}
Software written for reliable connectivity behaves badly on unreliable connectivity, and the differences are observable.
A well-built application handles a dropped connection gracefully — retaining unsaved input, retrying, and telling the user clearly what happened rather than losing their work.
A poorly built one loses a half-completed form when the connection drops, which is infuriating and eventually causes people to stop using it, so a cloud property management software Kenya should be tested under deliberately poor conditions during evaluation.
Test it directly. Disconnect during data entry, on a slow connection, and mid-save, and observe what happens, because a cloud property management software Kenya vendor’s demo will always run on their good connection.
Page weight matters too. An application loading large amounts of data on every screen is slow on a constrained connection, and a cloud property management software Kenya designed with that in mind performs noticeably better in real conditions.
Offline Capability and Sync {#offline-sync}
Genuine offline capability lets work continue without a connection and synchronises when one returns.
It is uncommon in property software and valuable where it exists, particularly for field staff.
The realistic scope is field tasks rather than the whole system. A caretaker logging a maintenance issue, capturing a meter reading or completing an inspection should be able to do so without a connection, and a cloud property management software Kenya with offline field capability captures data that would otherwise be written on paper and entered later or not at all.
Conflict handling matters where offline editing is possible. If two people change the same record while disconnected, the system needs a rule, and a cloud property management software Kenya should be explicit about how it resolves that rather than silently discarding one change.
Where offline is unavailable, a documented manual fallback is the substitute. A paper form for meter readings during an outage, entered afterwards, is unglamorous and prevents lost data, and any cloud property management software Kenya deployment should have that procedure written down.
Mobile Access for Field Staff {#mobile-access}
Property management is field work, and mobile capability determines whether field data reaches the system.
Caretakers, inspectors and property managers all work away from a desk, and requiring them to return to an office to record anything guarantees delay and loss.
The mobile experience needs to cover the field actions: log a fault, complete an inspection, capture a reading, photograph a condition, confirm a task, and look up a tenant, and a cloud property management software Kenya whose mobile view is a shrunken desktop interface will not be used at a gate in the sun.
Device reality shapes the requirement. Where caretakers use basic handsets, an SMS channel reaches them where an app does not, and a cloud property management software Kenya offering that fallback covers your whole team rather than the smartphone half.
Photograph upload is the specific stress point, since image-heavy field capture is exactly what a constrained connection handles worst, and a cloud property management software Kenya should queue uploads and retry rather than failing the whole task.
Data Consumption and Bundle Cost {#data-consumption}
Data cost is a real operating expense where staff use mobile connections, and it is routinely ignored in software evaluation.
A heavy application consuming substantial data per session becomes expensive across several field staff over a month.
Where staff pay for their own bundles, a data-hungry system simply gets avoided, and a cloud property management software Kenya that nobody uses in the field produces no field data regardless of its capability.
Either provide bundles as a cost of the deployment or choose a lightweight system, and preferably both, since a cloud property management software Kenya designed for efficiency plus a small monthly allowance removes the objection entirely.
Ask vendors about typical data consumption per user per month. Few will have measured it, which is itself informative about how carefully the cloud property management software Kenya was built for this market.
Power Interruption and Access Continuity {#power}
Power failures take out your router before they take out anything else, and cloud access ends immediately.
The office mitigation is a small uninterruptible supply for the router and switch, which is inexpensive and keeps connectivity alive on laptop batteries.
Mobile data on a phone is the secondary fallback, allowing critical work to continue from a handset during an outage, and a cloud property management software Kenya with a usable mobile interface makes that realistic rather than theoretical.
The vendor’s own power resilience matters equally. A hosting provider with proper redundancy is unaffected by local outages, which is genuinely an argument for cloud property management software Kenya over an on-premise server in a building with unreliable power.
Plan the critical functions. Knowing which tasks must continue during an outage — recording a payment, checking a tenant balance — and having a way to do them is what turns an outage into an inconvenience, and a cloud property management software Kenya deployment plan should identify them.
Uptime Commitments and What They Mean {#uptime}
Vendors quote uptime percentages, and the numbers are less reassuring than they sound once translated.
Ninety-nine percent uptime permits several hours of downtime monthly. Ninety-nine point nine permits well under an hour. The difference matters if the downtime lands on the first of the month.
Ask what the commitment actually covers and what is excluded. Scheduled maintenance is usually excluded, and a cloud property management software Kenya with generous maintenance windows may be unavailable more than the headline suggests.
Ask when maintenance is scheduled. Maintenance during Kenyan business hours is a different proposition from maintenance overnight local time, and a vendor operating in a distant time zone may schedule at exactly the wrong moment for a cloud property management software Kenya user here.
Ask for historical performance rather than only a commitment. A published status history showing actual incidents is more informative than a contractual promise, and a cloud property management software Kenya vendor confident in their record will share it.
Remedies for breach are usually service credits, which do not compensate for a lost collection day, so the practical protection is choosing a reliable provider rather than relying on the clause.
Security: What to Actually Ask {#security}
Security claims are easy to make and harder to substantiate, so the questions should be specific.
Ask how authentication works and whether multi-factor authentication is available and enforceable for administrative accounts.
Ask whether they have undergone any independent security assessment and whether they will share the outcome, since a cloud property management software Kenya vendor who has never had an external review is relying on their own assurance.
Ask about their incident history and their breach notification process. A vendor who says they have never had an incident is either very fortunate or not telling you, and how a cloud property management software Kenya provider handles disclosure matters more than whether incidents occur.
Ask about their own staff practices — background checks, access logging, offboarding — because the most common route to data exposure is people rather than technology.
Your own practices matter as much. Weak passwords, shared logins and accounts left active after staff leave defeat any vendor security, and a cloud property management software Kenya is only as secure as the least careful person with access.
Access Control and Internal Permissions {#access-control}
Granular permissions are a security control as much as an operational one.
Different roles need different access — a caretaker needs tasks, an accounts person needs payments, an owner needs their own units only, and a manager needs the whole picture.
Owner scoping is the specific requirement in mixed-ownership portfolios. An owner seeing another owner’s units is a serious failure, and a cloud property management software Kenya with proper per-owner data scoping is essential rather than optional.
Administrative access should be limited and logged. The ability to alter payout destinations, void payments or export the entire database should sit with very few people, and a cloud property management software Kenya that logs every such action gives you an audit trail.
Offboarding is the procedure most often forgotten. A departed employee whose account remains active is an open door, and a cloud property management software Kenya deployment needs a written offboarding step that removes access the same day.
Encryption in Transit and at Rest {#encryption}
Two distinct protections apply, and vendors sometimes conflate them.
Encryption in transit protects data moving between your browser and the service, and it should be standard on any credible product.
Encryption at rest protects data stored on the vendor’s systems, so that a compromised storage device does not expose readable records, and a cloud property management software Kenya should be able to confirm both.
Ask specifically about both rather than accepting a general assurance that data is encrypted, since that phrase covers either or neither.
Backups need the same protection. An encrypted database with unencrypted backups is protected only until someone accesses a backup, and a cloud property management software Kenya vendor should confirm that backups are encrypted too.
Backup, Recovery and Restoration Testing {#backup-recovery}
Automatic backup is a headline benefit of cloud, and the detail determines whether it is real.
Ask how often backups are taken, how long they are retained, where they are stored, and whether they are held in a separate location from the primary data.
The critical question is whether restoration has been tested. A backup that has never been restored is an assumption rather than a protection, and a cloud property management software Kenya vendor who has actually performed a test restore can tell you how long it took.
Ask about recovery objectives — how much data could be lost in a failure, and how long recovery would take — since those two numbers describe your actual exposure with a cloud property management software Kenya far better than the word backup.
Consider your own export as an additional safeguard. A periodic export held by you protects against vendor failure as well as data loss, and a cloud property management software Kenya that supports scheduled exports makes that habit easy to maintain.
Vendor Personnel Access to Your Data {#vendor-access}
Somebody at the vendor can see your data, and the question is who and under what controls.
Support staff routinely need access to diagnose problems, which is legitimate and should be governed.
Ask whether access requires your authorisation, whether it is logged, and whether you can see the log, since a cloud property management software Kenya where support can view tenant records without any record of having done so is a governance gap.
Ask what happens to data used for testing or development. Production data copied into a test environment is a common and poorly controlled exposure, and a cloud property management software Kenya provider should either not do it or anonymise properly.
Contractual commitments matter here. Confidentiality obligations, restrictions on use of your data, and a commitment not to use it for other purposes should be in the agreement rather than assumed of any cloud property management software Kenya vendor.
Multi-Tenancy and Data Separation {#multi-tenancy}
Most cloud products serve many customers from shared infrastructure, which is efficient and requires proper separation.
The concern is whether one customer can access another’s data through a fault or a flaw.
Ask how separation is implemented and whether it has been tested, since this is precisely what an independent security assessment of a cloud property management software Kenya would examine.
Dedicated instances are offered by some vendors at higher cost, giving stronger separation, which is worth considering for portfolios where data sensitivity justifies it, though a properly built shared cloud property management software Kenya is not inherently unsafe.
Ask what happens on a customer’s departure, because data from a departed customer lingering on shared infrastructure is a housekeeping failure that a good cloud property management software Kenya provider will have addressed.
Integration and API Access {#integration-api}
A cloud system’s value increases with what it connects to, and integration capability should be assessed at selection.
The locally relevant integrations are mobile money for collection and disbursement, SMS and messaging for tenants and staff, accounting export, and bank statement import.
Mobile money callback handling is the specific technical requirement that makes automatic payment recording possible, and a cloud property management software Kenya without reliable callback processing will always have a manual step.
An open documented API is the safety net for everything not natively supported. It lets you build what you need later, and a cloud property management software Kenya with published API documentation is more adaptable than one with a fixed integration list.
Ask whether API access carries an additional charge, since some vendors restrict it to higher tiers, and discovering that after selecting a cloud property management software Kenya constrains your options.
Vendor Lock-In and Data Portability {#lock-in}
Lock-in accumulates quietly, and its cost is only felt when you try to leave.
The sources are data volume, integration dependencies, staff familiarity and configuration effort.
Data portability is the protection you can actually secure. Ask what export formats are available, whether the export includes everything — leases, payments, documents, history — and whether it costs anything, and get the answer in the contract for any cloud property management software Kenya you adopt.
Document export is where most systems disappoint. Structured data usually exports adequately while attached documents frequently do not, and a cloud property management software Kenya holding years of leases and inspection photographs that cannot be extracted has locked you in effectively.
Test the export during evaluation rather than trusting the answer. Requesting a sample export from a trial account tells you what you would actually receive from a cloud property management software Kenya if you left.
Exit Planning Before You Enter {#exit-planning}
Planning the exit at the start is unromantic and is what keeps the relationship healthy.
Establish before signing: what notice is required, what happens to your data on termination, how long it is retained afterwards, in what format it is returned, and what it costs.
The retention question cuts both ways. You want your data returned, and you want it deleted from their systems afterwards, and a cloud property management software Kenya agreement should address both explicitly.
Non-payment scenarios need covering too. Whether access is suspended or data deleted if a payment is late matters, and a cloud property management software Kenya that deletes on a missed payment is holding your business records hostage to an invoice.
Keep your own periodic export regardless of contractual terms, since the fastest exit is one where you already hold the data, which any cloud property management software Kenya supporting scheduled exports makes routine.
Vendor Viability and Continuity Risk {#vendor-viability}
Software businesses fail, and a failed vendor takes the service with it.
Assess viability proportionately to your dependence. A large established provider carries different risk from a two-person startup, and both can be reasonable choices with different mitigations.
Ask how long they have operated, roughly how many customers they serve, and whether they will provide references you can call, since a cloud property management software Kenya vendor with a real customer base will produce them readily.
Source code escrow arrangements exist for critical systems, though they are rarely practical for small deployments, and the more realistic protection for a cloud property management software Kenya user is a current export held independently.
Acquisition is the more common outcome than failure, and it can change pricing, support and roadmap significantly, so contract terms that survive a change of ownership are worth asking for when adopting a cloud property management software Kenya.
Update Cycles and Change Management {#updates}
Continuous updating is a benefit and occasionally a disruption.
Changes arrive without you choosing them, which mostly means improvements and occasionally means a workflow your staff knew has moved.
Ask how changes are communicated and how much notice significant ones receive, since a cloud property management software Kenya that changes a core screen without warning during a collection week creates avoidable friction.
Ask whether a test environment is available for larger changes, which matters more for portfolios with configured workflows, though a cloud property management software Kenya serving smaller operations may reasonably not offer one.
Feature requests and roadmap influence are worth asking about. A vendor serving this market who takes local requirements seriously will have a mechanism, and a cloud property management software Kenya built for another market and sold here may not.
Support Availability and Time Zones {#support}
Support quality shapes the experience more than feature count, and availability is the first component.
Ask what hours support operates, in which time zone, through which channels, and what response times apply.
Local time zone coverage matters practically. A vendor supporting you from a distant time zone will not answer during your collection week morning, and a cloud property management software Kenya with local business hours support is materially more useful.
Channel matters too. Email-only support is slow for an urgent problem, and a cloud property management software Kenya offering phone or messaging contact resolves issues faster.
Ask about implementation support specifically, since the first weeks generate the most questions, and a cloud property management software Kenya with dedicated onboarding assistance produces far better adoption than one that hands you a login.
Migrating From Desktop or Spreadsheets {#migration}
Most adopters are moving from something, and the migration is where projects fail.
The sources are typically a desktop program, a set of spreadsheets, or paper records, each presenting different extraction problems.
Data preparation is the largest task and it belongs to you rather than the vendor. Cleaning tenant records, reconciling balances and standardising unit names before loading is what determines whether the cloud property management software Kenya starts with reliable data.
Opening balances are the critical accuracy point. An incorrect balance produces a dispute with a real tenant, so reconcile them unit by unit against existing records before going live.
Sequence by property rather than loading everything at once, verify each before proceeding, and set a firm cutover date once verified, because running parallel indefinitely means neither record is trusted and the cloud property management software Kenya never becomes the source of truth.
Historical data needs a decision. Loading several years of history is expensive and often unnecessary, and keeping the old system readable for reference while starting the cloud property management software Kenya with current balances is frequently the pragmatic choice.
Running a Proper Evaluation {#evaluation}
Evaluation should test the deployment characteristics rather than only the features.
Run a trial with real data on a subset of properties, over a full billing and collection cycle if possible.
Test on your actual connectivity from your actual locations, including a caretaker’s phone in the field, since a cloud property management software Kenya that performs well in a demo may not on a mobile connection at an outer estate.
Deliberately test failure. Disconnect mid-entry, work on a weak signal, and see what a cloud property management software Kenya does when things go wrong rather than only when they go right.
Involve the people who will use it daily. A system the owner likes and the accounts person finds slow will be worked around, and their verdict predicts adoption better than any evaluation matrix.
Request the export during the trial, call two local references of comparable size, and get the hosting location, uptime history and exit terms in writing before committing to any cloud property management software Kenya.
Total Cost Over Several Years {#total-cost}
Monthly subscription pricing understates the commitment, and the honest comparison is over several years.
Per-unit pricing in this market commonly runs somewhere around KES 50–300 per unit per month depending on depth, with volume discounts at scale.
Multiply by your realistic unit count over three to five years, including growth, and compare against alternatives, because a cloud property management software Kenya at the upper end for a growing portfolio becomes a substantial recurring commitment.
Add the costs that sit outside the subscription: implementation and data migration, training, SMS charges, mobile money transaction fees, data bundles for field staff, a backup internet connection and any integration work.
Then weigh it against what it recovers — arrears caught earlier, rent reviews applied on time, void days reduced, administrative hours reclaimed — since a cloud property management software Kenya that prevents a few of those routinely returns more than it costs, but the calculation should be done rather than assumed.
Watch for pricing that escalates with growth in ways you did not anticipate, and ask what happens to your rate at renewal, because a cloud property management software Kenya priced attractively at forty units may be repriced at four hundred.
Data Protection Compliance Obligations {#data-protection}
Adopting cloud software does not transfer your obligations as a data controller, and this is widely misunderstood.
You remain responsible for the personal data you hold about tenants, owners and staff, regardless of who processes it on your behalf.
That responsibility includes ensuring your processor handles data appropriately, which means the contractual terms with your cloud property management software Kenya provider matter legally rather than only commercially.
Practical steps within your control are collecting only what you need, restricting internal access by role, defining a retention period rather than accumulating indefinitely, and being able to respond if someone asks what you hold, all of which a cloud property management software Kenya should support through configuration.
Arrears data deserves particular care given its sensitivity, and owner-visible tenant information should be scoped deliberately rather than exposing everything a cloud property management software Kenya holds.
Your specific obligations, including any registration requirements and the position on cross-border transfer, are a matter for qualified professional advice rather than for a vendor to determine on your behalf.
Contract Terms Worth Negotiating {#contract-terms}
Several terms are negotiable more often than buyers assume, and asking costs nothing.
Contract length and notice period come first. Monthly terms until the system has proven itself, moving to annual for a discount afterwards, is a reasonable position with any cloud property management software Kenya vendor.
Price protection on renewal is worth seeking, particularly where your portfolio will grow, since an uncapped rate increase at renewal is a lever you have handed over.
Data return and deletion terms should be explicit, covering format, completeness, timeframe and cost, and a cloud property management software Kenya provider unwilling to commit on these is telling you something.
Uptime commitments, maintenance window timing, support response times and breach notification obligations all belong in the agreement rather than in a sales conversation.
Have the agreement reviewed properly before signing. The terms governing your data, your exit and your liabilities are legal matters, and a qualified adviser reading the cloud property management software Kenya contract is a small cost against what it governs.
Frequently Asked Questions {#faqs}
Where should my data be hosted?
Ask the vendor which country, get it in writing, and take advice on the position — property data is personal data and cross-border transfer carries obligations under the Data Protection Act. Local or regional hosting also reduces latency noticeably.
What happens when the internet goes down?
Work stops unless you have planned for it. A backup mobile connection, a small uninterruptible supply for the router, and offline capability for field tasks are the practical mitigations, plus a written manual fallback for critical functions.
Is cloud secure enough for tenant records?
It can be, and often more so than a desktop machine with no backups. Ask specifically about multi-factor authentication, encryption in transit and at rest including backups, independent security assessment, staff access controls and breach notification, rather than accepting a general assurance.
How do I avoid being locked in?
Establish before signing what export formats exist, whether documents as well as data are included, what it costs and how long it takes. Test the export during your trial, and keep a periodic export of your own regardless.
What does it actually cost?
Per-unit pricing commonly runs roughly KES 50–300 per unit monthly with volume discounts. Multiply over three to five years including growth, and add implementation, training, SMS, transaction fees, field data bundles and a backup connection for the real figure.
Does the vendor’s compliance make me compliant?
No. You remain the data controller and retain your obligations regardless of who processes the data for you. Your contractual terms with the vendor matter legally, and your specific position needs qualified advice.
What uptime should I require?
Ask what the number covers, what is excluded, when maintenance is scheduled and in which time zone, and request historical performance rather than only a commitment. Service credits do not compensate for a lost collection day, so choose reliability over remedies.
Should I migrate all my history?
Often not. Loading several years of history is expensive and frequently unnecessary. Starting the cloud property management software Kenya with accurate current balances while keeping the old system readable for reference is usually the pragmatic choice.
