Property Flow shut down — the 90-day recovery playbook for Thai real estate agencies
Property Flow ceased operations on 31 December 2023, leaving Thai property agencies stranded. A practical 90-day playbook for salvaging your data, rebuilding portal integrations, and choosing a vendor that won't disappear next.
TL;DR
Property Flow, a Bangkok-based real estate SaaS that served Thai property agencies from roughly 2016 to 2023, shut down on 31 December 2023. If you were a Property Flow customer and missed the export window, your historical pipeline data is gone — but your business isn't. This is a practical 90-day playbook for the agencies still working through this: salvage what's recoverable, reconstruct your active pipeline, choose a vendor that won't repeat the pattern, and migrate without freezing operations. Sections cover data triage, pipeline reconstruction, vendor evaluation, and the migration timeline that's worked for the Property Flow refugees we've onboarded in 2026.
What happened to Property Flow
Property Flow operated as a B2B end-to-end real estate platform from approximately 2016, offering inventory management, lead capture, automatic data entry, multi-platform sales posting, and team collaboration for Thai property agents, brokers, and developers. It was a credible product with a real Thai-market focus — exactly the kind of vendor that a Bangkok or Phuket agency would have picked over HubSpot or Salesforce in 2020.
On 31 December 2023, all Property Flow operations ceased. The company didn't publicly disclose detailed reasons. Based on the broader context — post-COVID Thai real estate market compression, increasing competition from international SaaS entrants, and the unit-economics challenge of selling SaaS into a relatively small Thai market — the shutdown reflects a hard truth about the Thai PropTech space: vendors with single-country focus and limited capital have a tighter margin for error.
If you were a Property Flow customer, this isn't useful in itself. What's useful is the question: what do I do now?
Phase 1: Emergency triage (Days 1–14)
Step 1 — Salvage what's recoverable
If you exported your Property Flow data before the wind-down window closed, skip this section. If you didn't, here's where your data actually lives:
- DDproperty + Hipflat: Active listings you had published are still in those portals. Log in to your DDproperty and Hipflat broker accounts and export the listing inventory. This recovers property addresses, photos, prices, and descriptions.
- Accounting software: Past 12 months of closed deals are in your bookkeeper's records — buyer name, property address, commission paid, transaction date. This reconstructs your "completed deals" history.
- Bank statements: Reservation deposits, escrow transfers, and commission payments show the full transaction parties and amounts. Cross-reference with accounting.
- Agent personal devices: LINE chat history with prospects often lives on agents' phones for months. Export the LINE chat archives. This recovers the lead-conversation context.
- Email archives: Quote PDFs, proposal documents, and contract drafts you sent prospects are in your sent folder. Search for "Property Flow" or your agency name to surface them.
- Local Excel backups: If you used Property Flow's export feature ever (e.g. for accountant year-end), check shared drives and email attachments from past tax seasons.
Realistic expectation: with this approach, most agencies recover 60-80% of their historical data — enough to rebuild active relationships and re-engage past clients, even if granular analytics are gone.
Step 2 — Reconstruct your active pipeline by phone
The active pipeline is the highest-value data you've lost — the 80–150 prospects who are mid-decision. Most Thai agencies remember the major ones by name, but the long tail is fuzzy.
Method: each agent writes down every active prospect they can recall from the last 90 days. Cross-reference with LINE chat archives (Step 1). For prospects with active interest, a phone call within 14 days of shutdown re-establishes the relationship. Frame it honestly: "We're upgrading our system after our previous vendor went out of business — I want to make sure I have your current details and the property you were looking at." Most prospects respond well to this; some appreciate the proactive contact.
What you'll likely lose in this phase: lukewarm prospects from 90+ days ago who weren't yet hot enough for an agent to remember. That's painful but recoverable through future lead-gen.
Step 3 — Set up basic new-CRM tenant
You need somewhere to put the data you're recovering. By Day 7–10, you should have a new CRM tenant provisioned with your branding, agent accounts, and basic property inventory imported from your DDproperty/Hipflat re-exports. The point isn't to be done — it's to have a destination for incoming work while you complete the migration.
Vendor selection criteria specific to a post-shutdown agency: pick one with explicit data-portability guarantees in writing, a multi-year operational history (not a stealth startup), and a clear Thai-market focus. We cover this in detail in Phase 2.
Phase 2: Full migration (Days 15–45)
Step 4 — Choose your new CRM with explicit shutdown-resistance criteria
You've now lived through what most agency owners only fear. The vendor-evaluation lens shifts permanently: it's no longer "what features does it have?" but "what happens if this vendor disappears?" Five signals that dramatically reduce shutdown risk:
- Vendor is profitable today. Ask directly: "Are you cash-flow positive?" Vendors dependent on raising venture rounds to fund operations have failure modes you can't see from the outside.
- Vendor has independent ownership. VC-controlled startups operate on an exit timeline that doesn't include "small Thai market matters." Independent or bootstrapped vendors are more aligned with your continuity.
- Vendor publishes data-portability guarantees in writing. The contract should specify: nightly CSV export to your storage, full SQL dump on demand, defined export window (180+ days) in case of shutdown. If it's not in the contract, it doesn't exist.
- Vendor's tech stack is mainstream. Postgres database, REST API, Excel/JSON exports = your data is rescuable by any successor vendor. Proprietary lock-in formats = you're trapped.
- Vendor's Thailand presence is real. Thai-resident team, Thai-language Customer Success, local-hours support. Vendors with no local footprint can deprioritize a small market when other priorities arise.
DevProp publishes all five publicly. We're operationally profitable, independently owned, contractually guarantee nightly CSV export plus full SQL dump on demand, run on Postgres + REST, and have a Bangkok-based team. These aren't features — they're insurance.
Step 5 — Rebuild your portal connections
DDproperty and Hipflat connections need to be re-bound to your new CRM. Process:
- DDproperty: Contact your DDproperty broker account manager. Request API access for the new CRM (if your new CRM supports the connector natively, this is a 1-day setup). Map your existing listings to the new CRM's inventory.
- Hipflat: Similar process via Hipflat's broker partner team. Listings can be re-pushed from the new CRM in batches.
- LINE Official Account: If you had a LINE Official under Property Flow's webhook, re-bind it to your new CRM's webhook URL via the LINE Developers Console. Existing follower base is preserved.
- WhatsApp Business: Re-link the phone number to the new CRM's WhatsApp Business API integration.
Total time for portal rebuilds: 5–10 days if your new CRM supports each integration natively. Significantly longer if you have to build custom webhook bridges.
Step 6 — Re-onboard your team
Agents are tired from the shutdown. Training on a new CRM right after losing the old one is morale-sensitive. Best practice: short focused sessions, not marathon workshops. We recommend three 90-minute sessions over Week 4–5:
- Session 1 — Basic flow: capturing a new LINE lead, scheduling a viewing, updating deal status.
- Session 2 — Contract execution: generating a contract from template, sending for Thai ETA e-signature, archiving the executed PDF.
- Session 3 — Portal publishing: creating a new listing, publishing to DDproperty/Hipflat, handling price changes.
By Day 45, the team is operating fluently in the new system.
Phase 3: Operational stability (Days 46–90)
The last 45 days are about returning to "normal" — building out the reporting and analytics that you took for granted before the shutdown.
- Reporting: Rebuild your monthly close-rate, pipeline-velocity, and source-attribution reports. The granularity will be lower at first (you don't have 12 months of historical data in the new system) but the data accumulates from Day 1 of the new CRM.
- Workflow refinement: Surface and fix the inefficiencies you didn't realize you had with Property Flow. Many agencies report that the forced migration revealed workflow improvements they'd been postponing.
- Documentation: Write down your new processes. The Property Flow shutdown exposed a gap most agencies had — institutional knowledge that lived only in the vendor's UI. The fix: document your workflows in your own wiki or Notion so future tool changes are less traumatic.
- Backup discipline: Configure your new CRM's nightly export to your own storage (S3, Google Drive, OneDrive). Verify the export actually works once a month. This is the discipline you wish you'd had with Property Flow.
The longer lesson
The Property Flow shutdown isn't a one-time event in Thai PropTech — it's a reminder of a structural reality. The Thai SaaS market is small. Vendors with single-country focus and limited capital have a thinner margin for error than vendors with broader market exposure or independent ownership. The risk doesn't go away by switching to an international vendor either — international vendors have their own failure mode (deprioritizing the Thai market when bigger countries demand attention).
The realistic strategy is: choose vendors with a credible long-term position (profitable today, independent ownership, real Thai presence), demand data-portability guarantees in writing, and maintain your own backups. Treat the CRM as infrastructure you depend on but don't trust blindly.
If you're working through a Property Flow migration right now and want a sounding board, we're happy to talk — no sales pitch required. Several of our customers in 2026 came from Property Flow, and we've refined the migration playbook in real conditions. Even if you choose a different vendor at the end, you'll have a better-defined evaluation criteria from the conversation.
Property Flow refugee? Get the migration kit free
Send us your Property Flow account name and we'll send back the recovery checklist, data-portability contract clauses to demand from your next vendor, and the Bangkok-team migration timeline — even if you choose a non-DevProp vendor.
Request the kit →