Making IRIS, CCH and Microsoft 365 actually like each other

Hosting practice software on infrastructure sized for general office use. Practice management workloads spike heavily at month-end and during busy season. A server that handles email and file shares comfortably for ten months a year will fall over when twenty fee-earners hit it at the same time.

Treating the database as a generic SQL Server. Each practice product has its own database tuning recommendations, indexing strategy and maintenance plan. Generic SQL Server best practice is usually close but not exact, and the difference shows up under load.

Leaving the Outlook add-ins to chance. Most practice products have an Outlook add-in for email filing, time recording or client lookup. They're often the source of mysterious crashes if the add-in version doesn't match the Outlook version. Standardising on a single Outlook version across the firm makes this less painful.

Treating the database backup as 'someone else's problem'. The Microsoft 365 backup, the file share backup and the practice database backup are three different things. All three need to be tested, ideally on different cadences.

There are three workable hosting models for practice software in 2026. On-premise with modern hardware, hosted by the vendor or a specialist host, or migrated to a cloud-hosted Windows server (Azure or a partner equivalent).

On-premise is still defensible for larger firms with strong IT capability and stable office locations. The downside is that hybrid working requires either a published app or RDS, and that adds another layer of complexity.

Vendor or specialist hosting solves the hybrid problem and offloads the infrastructure responsibility. The downsides are cost and the loss of some flexibility in how you integrate with Microsoft 365.

Azure-hosted Windows server is the popular middle ground for mid-sized firms. The performance is predictable, the integration with Microsoft 365 is clean, and the cost is reasonable. The complexity is that someone needs to manage the Azure environment competently, which is where a practice-aware partner earns their fee.

Outlook integration for email filing and time recording. Most practice products do this through an add-in; some are now using Microsoft Graph API and Power Automate. The Graph-based approach is more robust but newer.

SharePoint integration for client documents. The patterns vary widely. Some firms keep everything inside the practice DMS, some use SharePoint as the primary store with metadata sync, and some run a hybrid. None is universally right; the choice depends on workflow.

Teams integration for client communication. Increasingly important, particularly for hybrid working. Practice products are catching up on this, though some are further ahead than others.

Authentication via Entra ID with single sign-on. This is the unsexy plumbing that makes the rest of the stack feel coherent. When it works, nobody notices. When it doesn't, every login becomes a small irritation.

Most firms eventually migrate practice management software at least once. IRIS to CCH, CCH to IRIS, on-premise to hosted, hosted to Azure. The migration is the moment when years of accumulated habits get tested.

A practice-aware IT partner will treat the migration as a project of its own, not as an afterthought to a Microsoft 365 rollout or a server refresh. The data migration is rarely the hardest part; the cultural change of moving from one set of habits to another is.

Plan migrations for May, June or July. Not December. Not late September. Never January. The vendor will quietly thank you for picking a sensible date.

An IT partner that supports accountancy practices regularly knows the difference between an IRIS performance issue and a SQL Server performance issue. They know which version of CCH is stable and which one to wait on. They can read a practice software log file without having to Google every error code.

That's worth a meaningful premium over a generalist IT partner. The premium is paid back within the first busy season when something breaks and the recovery is measured in hours rather than days.

The practice software is fast. Outlook starts cleanly. Email filing works without thinking about it. Clients see a coherent document portal that matches the brand. Hybrid working is genuinely possible without a VPN wrestling match. Backups are tested. Upgrades happen on schedule, outside busy season.

None of this is glamorous. All of it is the difference between a practice that runs well and one that's permanently fighting its tools.

Practice software vendors are an underrated part of the picture. The strength of your relationship with the IRIS or CCH account manager affects how quickly issues get triaged, how informed you are about upcoming changes, and how much input you have on the roadmap.

A practice-aware IT partner usually has those relationships already. They know which vendor contact to ring when something is on fire, and which release notes to pay attention to. That access pays for itself in the moments that matter.