From Spreadsheets to a Property Management Platform

The Spreadsheet Era Ends Slowly, Then All at Once

Most property operators do not decide to leave spreadsheets. They grow past them. A portfolio of fifty units on one Excel file is manageable. Five hundred units across a dozen buildings on twelve interlinked files, each maintained by a different team member, is the plateau from which everything gets harder — reporting takes longer, errors multiply, and onboarding a new hire means teaching them a private filing system rather than a platform.

This playbook walks through how to move cleanly from that state onto ArkanPM without losing operational continuity.

Phase 1: Data Assessment

Before any import, inventory what you have and where it lives. A defensible assessment covers six datasets:

1. Portfolio and property structure — what portfolios exist, what properties sit under each, what buildings sit under each property
2. Unit registry — every unit with area, type, status, and rent
3. Owner and ownership records — who owns what, at what share, under what ownership type
4. Lease records — active and recently expired, with rent, deposit, dates, and escalation terms
5. Asset registry — the systems and equipment you expect to maintain
6. User and role inventory — who needs access, with what scope

For each dataset, capture: record count, primary location, update frequency, data steward, and known quality issues. The data steward is often the most important field on this list. Someone owns the quality of that data, whether or not you have said so out loud. Write it down.

Known Quality Issues Are Normal

Every spreadsheet portfolio has them: units that appear in the rent roll but not in the asset register, leases with inconsistent date formats, owner records with missing Emirates ID or IBAN fields. Do not try to fix all of this in the source spreadsheet before importing. Fix the critical errors, import, then clean up in the platform where the validation rules will actively help you.

Phase 2: Portfolio Hierarchy Setup

ArkanPM models real estate as a hierarchy: portfolios → properties → buildings → floors → zones → units. Set this up before any other import. Two rules:

• Do not flatten the hierarchy to match your spreadsheet — if your current file has a "Building" column but no portfolio or property layer, introduce those layers now. You will want them within six months regardless.
• Use real codes, not sequential numbers — portfolios and buildings should carry human-readable codes that match how your team actually refers to them. "ALP-01" is better than "Portfolio 1."

Define floors, zones, and units only after the parent structure is stable. Unit-level changes are cheap; restructuring the property hierarchy after you have imported 500 leases is not.

Phase 3: Role and User Mapping

ArkanPM ships with eleven built-in roles. Map every human who needs access to one of them:

• Super Admin, Platform Admin — platform operators, rarely used by single-tenant customers
• Tenant Admin — your senior operations leadership
• Facility Manager — cross-building operations roles
• Building Manager — scoped to assigned buildings
• Maintenance Technician — field staff
• Inspector — quality and compliance staff
• Vendor User — external service providers
• Owner — for the owner portal
• Resident — for the resident portal
• Read-Only — auditors, analysts, finance partners

Resist the urge to create custom roles on day one. Use the built-ins for sixty days, identify genuine gaps, then add custom roles with precise permission matrices. Most "we need a custom role" requests on day one turn out to be "we need building-scoped assignments" once you see how scoping actually works.

Building-Scoped Assignments

Building managers are assigned to specific buildings with optional expiration dates. ABAC handles the rest — a building manager querying work orders sees only their assigned buildings, automatically. You do not write any filtering logic to make this work. You just assign them correctly.

Phase 4: Bulk Imports

ArkanPM supports CSV imports for the high-volume datasets — assets being the canonical example, with success and error counts returned per batch. The pattern for every import is the same:

1. Export a small sample from the source
2. Map columns to ArkanPM fields
3. Import a 20-row test batch
4. Review errors and correct the template
5. Import the full dataset
6. Reconcile counts against source

Do not import in order of size. Import in order of dependency: portfolios before properties, properties before buildings, buildings before units, owners before leases, units before leases. If you import leases before the units they reference, you will spend an afternoon untangling orphaned records.

A Sample Import Sequence

Phase 5: Validation

After the imports complete, run three validations before going live:

• Occupancy reconciliation — every "occupied" unit should have exactly one active lease; every "vacant" unit should have zero
• Ownership coverage — every unit should have at least one ownership record summing to 100 percent
• Role coverage — every active user should have a role; no one should have more access than their job requires

If any validation fails, fix it in the platform. Do not go back to the spreadsheet. The platform is now the source of truth.

Phase 6: Cutover Strategy

The cleanest cutover is a hard one. Pick a date, freeze changes in the source spreadsheets for a short window, import, validate, and go live. Parallel operation — running both systems "just in case" — sounds safe and in practice causes the worst kind of drift: neither system is authoritative, and every decision gets made twice.

The exception is financial close. Finish the current accounting period in the legacy process, then cut over at period boundaries. This contains the reporting complexity to a clean break.

Phase 7: Integration Ecosystem Planning

ArkanPM does not replace your accounting system, your BMS, or your IoT stack. It integrates with them. Plan the integration map before go-live:

• ERP and accounting — for general ledger, accounts payable, and owner payouts
• BMS (Building Management Systems) — for operational data flowing into condition and meter readings
• IoT platforms — for sensor data feeding meter-based PM triggers
• Arkan Handover — if you are moving newly completed assets from Arkan's handover platform into ongoing operations

Integration sequencing depends on your operational pain. Start with whichever connection eliminates the most manual re-keying. For most operators, that is the accounting integration — the elimination of monthly journal-entry transcription from the rent roll alone justifies the project.

The Outcome

A clean migration is boring. The dashboards look similar to what the spreadsheets tried to show, the team learns new terminology, and then a quarter later you notice that the reports you used to produce on Thursday afternoons now produce themselves on Monday morning, the owner questions that used to take three days now take thirty seconds, and the hours your senior operations staff used to spend reconciling files are going into actual operations instead. That is the payoff. It is not glamorous, and it is worth every hour of the move.