Concurrent (Concurrent Property Management System)
Concurrent is a property management system used widely in UK PBSA and build-to-rent operations. Part of StuRents Group, it handles the full rental lifecycle: marketing, contracting, payments, tenancy management, and financial reporting. Its API makes it a key data source for operators building a connected commercial stack around HubSpot.
What does Concurrent do as a property management system?
Concurrent is an end-to-end PMS built for the rental market. It manages the full tenancy lifecycle: property marketing, digital contract signing, guarantor verification, rent collection, arrears tracking, maintenance logging, and financial reconciliation. Operators use it as the operational record of truth for every booking and tenancy. The platform holds tenant details, signed contracts, payment history, deposit records, and occupancy data, making it the primary source of resident data for most PBSA operators running on it.
Which operators use Concurrent?
Concurrent is part of StuRents Group, which also operates one of the UK's leading student accommodation marketplaces. It serves PBSA operators, residential letting agents, and, following a 2023 rebrand, build-to-rent and co-living providers. Its roots in the student sector mean it is widely adopted among PBSA operators that also list on the StuRents platform. For UK student accommodation operators in particular, Concurrent is one of the prominent PMS choices, and its prevalence in the sector makes it a natural integration target for any operator building a CRM-led commercial stack.
What is a Concurrent API, and why does it matter for operators?
Concurrent provides an API that allows authorised third-party tools to read tenancy, booking, occupancy, and financial data out of the system. This is what makes integrations possible. Without API access, tenancy data sits locked inside the PMS and must be exported manually; with it, that data can flow automatically into a CRM, a reporting tool, or a finance system. For operators trying to connect their commercial operations, the Concurrent API is the data pipeline that makes it viable.
How does Concurrent relate to HubSpot?
Concurrent and HubSpot serve different functions: Concurrent is the operational record for tenancies; HubSpot is the CRM for commercial relationships, marketing, and communications. Native connectivity between them is limited to new-enquiry hand-off, where an enquiry can be passed across to create a deal. Tenancy, booking, occupancy and payment data do not flow that way. Operators who want their CRM to reflect live tenancy and occupancy, rather than just the arrival of a new enquiry, need an integration layer to bridge the two. Without it, leasing and marketing teams work from incomplete data and commercial decisions lag operational reality.
Key takeaways
- Concurrent is an end-to-end PMS covering marketing, contracting, payments, tenancy management, and financial reporting, used widely across UK PBSA and rental markets.
- It is part of StuRents Group and follows the student accommodation sector, where it is one of the dominant system choices.
- Concurrent provides an API that enables authorised tools to pull tenancy, booking, occupancy, and financial data for integration with third-party systems.
- Native Concurrent-to-HubSpot connectivity covers new-enquiry hand-off only; surfacing tenancy, booking and occupancy data in the CRM still requires an integration layer.
- Cloudfox's StaySynced product provides a self-serve Concurrent-to-HubSpot integration, used by operators including Luna, Axo Student, Every Student, and Fusion Student.
How Cloudfox Helps With Concurrent
Cloudfox built StaySynced specifically to bridge Concurrent and HubSpot for PBSA operators. The integration connects to Concurrent's API on a recurring schedule, pulls tenancy and booking data, and pushes it into HubSpot so that contact records, deal stages, and occupancy figures stay current without manual exports. Setup is self-serve: operators authenticate their Concurrent account and the sync runs automatically. Customers including Luna, Axo Student, Every Student, and Fusion Student use this integration as part of their commercial stack.
Beyond the Concurrent integration, Cloudfox implements the full HubSpot stack for PBSA and BTR operators: custom pipelines, contact properties, inbox migration, and WhatsApp setup. If your operation runs on Concurrent and you want your CRM to reflect it, find out how we work at cloudfox.it/what-we-do.
Frequently Asked Questions About Concurrent
Is Concurrent the same as StuRents?
No. StuRents is a student accommodation marketplace where properties are listed and students search for rooms. Concurrent is a separate property management system, also owned by StuRents Group, used by operators to run tenancy operations. They are related products under one group but serve different purposes.
Does Concurrent connect directly to HubSpot?
Partly. Concurrent can hand a new enquiry across to HubSpot to create a deal. It does not send tenancy, booking, occupancy or payment data. Operators who want that data in HubSpot, or who want deal stages and contact records to track the tenancy lifecycle rather than just the initial enquiry, need an integration layer to connect the two systems.
How often does the Concurrent to HubSpot sync run?
The StaySynced integration with Concurrent syncs every two hours between 7am and 7pm. This cadence reflects a limitation of the Concurrent API itself rather than the integration tool.
Can PEX operators use the same integration?
PEX is a different property management system used by a smaller number of PBSA operators. StaySynced also integrates PEX with HubSpot, but that is a separate custom engagement rather than the self-serve Concurrent product.
What data flows from Concurrent into HubSpot?
The integration pulls tenancy and booking data from Concurrent and surfaces it in HubSpot against the relevant contact and deal records. The exact fields depend on your implementation setup.