- Client
- Argyll
- Sector
- Flexible workspace · property
- Engagement
- Via JADe, now OpsTech
- Period
- 2020 – present
The situation
Argyll's sales team works in Dynamics 365. When Elephas first became involved in 2020, a Dynamics 365 Sales implementation was struggling, and it needed integrating with Dynamics NAV, ClickDimensions, TxtSync and RingCentral.
Argyll later moved its buildings, members and contracts from NAV to Yardi Kube. From then on, every deal closed in CRM had to become a company, members and a contract in Yardi — and every renewal, amendment and termination in Yardi had to flow back. If the two systems drift apart, occupancy and pipeline figures stop being trustworthy.
What we did
- Delivered the Dynamics 365 Sales implementation and its four integrations
- Designed and built .NET 8 middleware on Azure App Service between Dynamics 365 and Yardi Kube
- Pushed deals closed in CRM to Yardi, with Yardi's changes flowing back through webhooks and Power Automate
- Encoded the licence lifecycle, so renewals, amendments, future-dated terminations and repeated webhooks are all handled safely
- Converted CRM's month-based price steps into Yardi tiered pricing, pro-rated for mid-month starts
- Built reconciliation tooling that checks every building, runs as a dry run first and saves a rollback snapshot before writing anything
The outcome
A single reconciliation run across all 24 buildings applied 1,321 corrections with no errors. Along the way, intermittent authentication failures were traced to up to 73 seconds of clock drift between the vendor's load-balanced servers — the kind of fault that looks random until someone measures it.
Kept on when the contract changed hands
When Argyll moved its technical services to OpsTech, OpsTech's first step was to subcontract the integration back to Elephas.