Technology · Primafact

Primafact Support for Ontario Litigation Firms

Primafact holds the working file for a litigation practice. We support everything underneath it: the server, the storage, the network, remote access, and the backups that make a bad day survivable. Application defects and licensing stay with the vendor, and we coordinate those cases on your behalf.

Serving Greater Sudbury, Northern Ontario, and surrounding communities. Remote support available throughout Ontario.

A personal-injury or litigation file can run to thousands of scanned pages. Primafact makes that volume workable, but only if the infrastructure serving it keeps up. When it does not, the symptom is always the same: a clerk clicks a document, waits, and the whole team quietly loses an hour a day.

We are not a Primafact reseller and we do not write the software. What we do is make the environment around it fast, secure, and recoverable, and act as the firm's technical contact when a vendor case needs raising.

That work covers server and storage sizing for document growth, performance diagnosis using real measurements rather than guesses, secure access for lawyers working from home or from court, and backups that have actually been restored in a test.

Why Primafact performance problems are usually infrastructure problems

Before recommending anything, we measure. Storage latency on the case-file volume, link speed and duplex on every hop between workstation and server, memory pressure on the server, and the time a real file takes to open from a real desk. Those four numbers explain the large majority of complaints.

The usual findings are unglamorous. Case data sitting on aging spinning disks. A switch port stuck at 100 Mbps because of a damaged patch cable. Antivirus inspecting every page image on open, with no vetted exclusions in place. Or remote users on a VPN pulling entire documents across a residential upload link when a published-desktop session would have moved nothing but pixels.

  • Storage latency and throughput on the case-file volume
  • Switch port speed, duplex, and cabling quality end to end
  • Server memory, CPU, and concurrent-session headroom
  • Antivirus exclusions applied safely and documented with the vendor's guidance
  • Remote-access method compared against real file-open times
  • Workstation specification for the staff who live in the software all day

Sizing storage for how litigation files actually grow

Scanned medical records and productions do not shrink. A firm that adds a handful of substantial files a month will outgrow storage that looked generous at purchase, and running a case-file volume near capacity is both a performance problem and a risk.

We plan capacity over a three to five year horizon, keep the active case store on solid-state storage, and monitor growth so the conversation about the next expansion happens in a budget meeting rather than on the morning a volume fills.

Backup and retention built for litigation files

A file-level copy of an open case store is not a backup. We use application-aware, image-level backup so the server is captured in a consistent state, keep an offsite copy on immutable storage that ransomware cannot rewrite, and set retention to match how long litigation files genuinely need to be recoverable rather than accepting a vendor default.

Then we restore. A backup that has never been tested is a belief, not a control, so restores are rehearsed and the results are written down where the firm can see them.

Access, confidentiality, and departing staff

Client confidentiality obligations do not pause when a laptop leaves the office. Multi-factor authentication on every account, encrypted devices, role-based access to case data, and a documented offboarding routine are baseline for a firm handling privileged material.

Offboarding is the step most firms find uncomfortable in hindsight. Knowing exactly which accounts, devices, and remote sessions a departing clerk or lawyer had, and closing all of them the same day, is far easier when it was designed in advance.

What's included

Performance Diagnosis

Measured storage, network, and workstation analysis that finds the real cause of slow file opens.

Server Design & Sizing

Host specification matched to document volume and concurrent users, verified against current vendor requirements.

Storage Capacity Planning

Solid-state case-file storage with growth monitoring so the volume never runs to the edge.

Server Migration

Planned moves to new hardware with rehearsed data transfer, off-hours cutover, and verified workstation access.

Backup & Tested Restores

Application-aware image backups, immutable offsite copies, and restores proven in a test rather than assumed.

Remote & Court Access

Published-desktop or VPN access chosen on measured performance with real case files.

Network & Cabling

Switching, cabling, and Wi-Fi that can carry large document sets without stalling.

Confidentiality Controls

MFA, encryption, role-based access, and same-day offboarding for departing staff.

Scanning & Intake Workflow

Scanner, OCR, and intake configuration so records reach the case file cleanly the first time.

Vendor Coordination

We raise and manage Primafact support cases on the firm's behalf when the application itself is at fault.

Documentation

Written environment documentation covering versions, storage layout, backup jobs, and recovery steps.

Practice-Wide IT

The rest of the firm's technology, including Microsoft 365, accounting software, and endpoints, under one plan.

Who it's for

  • Personal-injury and litigation firms running Primafact on a server
  • Firms where document volume has outgrown the original hardware
  • Practices with lawyers working from home, from court, or from a second office
  • Firms planning a server replacement or a move off aging hardware
  • Small and mid-size firms with no internal IT staff
  • Firms that have never tested a restore of their case data

Common problems we solve

  • Case files that take too long to open, especially large medical productions
  • Storage volumes running close to full with no growth plan
  • Remote access that is unusably slow over a home connection
  • Backups that copy folders rather than capture the server consistently
  • No clear owner when something breaks, so the firm bounces between vendors
  • Antivirus configured without vetted exclusions, slowing every document open
  • Departing staff whose access was never fully closed
  • Undocumented environments where nobody knows how recovery would work

Why Nickel City Tech Solutions

  • Clear boundary between vendor application support and infrastructure support, in writing
  • Performance work driven by measurement rather than replacing hardware on a hunch
  • Backup and restore testing treated as a routine control, not a sales feature
  • Northern Ontario team available on site across Greater Sudbury and the surrounding region
  • Experience supporting the wider legal stack, including PCLaw, Microsoft 365, and document management
  • Predictable monthly pricing rather than surprise project invoices
Supported technologies

Technologies we support in this industry

The platforms and line-of-business systems we most often support for this sector. Every entry links to what we do, the services it falls under, and related reading.

Browse all supported technologies

Frequently asked questions

What is Primafact?

Primafact is litigation document and evidence management software used widely by Ontario personal-injury and litigation firms. It stores scanned medical records, productions, transcripts, and correspondence in a searchable case file, with tools for highlighting, summarizing, and building briefs. It is the working file for a litigation team, which is exactly why the infrastructure underneath it matters.

Do you provide Primafact support, or does the vendor?

Both, with a clear line between them. Primafact's own vendor support owns the application: software defects, feature questions, version upgrades, and licensing. We own the environment the application depends on: the server, the storage, the network, the workstations, the backups, and remote access. Most day-to-day complaints, especially slowness, turn out to sit on our side of that line.

Why is Primafact slow at our firm?

Almost always storage, network, or workstation resources, rather than the software itself. The common culprits are a case file store on spinning disks or a saturated NAS, a gigabit link that is actually negotiating at 100 Mbps, antivirus scanning every page image as it opens, VPN latency for remote users, or workstations with too little RAM to hold large document sets in memory. Each has a different fix, and each is measurable before anyone spends money.

What server does Primafact need?

It depends on firm size and document volume rather than lawyer count alone. A litigation practice scanning thousands of pages per file accumulates storage quickly, so we size for growth over three to five years, put the case store on solid-state storage, and make sure the server has enough memory and network throughput to serve concurrent users. We confirm the current published requirements with the vendor before any purchase rather than working from an old spec sheet.

How should Primafact data be backed up?

With an application-aware, image-level backup that captures the server in a consistent state, plus an offsite copy on immutable storage. Copying live case-file folders with a file sync tool is not a backup: open files get skipped, and a ransomware event replicates straight into the copy. Litigation files also have long retention expectations, so retention needs to be deliberate rather than a default 30 days.

Can our lawyers use Primafact from home or from court?

Yes, and the method matters. Because Primafact works with large document sets, a plain VPN mapped to a file share often performs poorly over a home connection. A published desktop or remote-session approach, where the application runs beside the data and only the screen travels, is usually far faster. We design for whichever fits the firm and test it with real files, not a sample folder.

Can you help us move Primafact to a new server?

Yes. We plan the migration with the firm and the vendor: current version check, storage sizing, a rehearsal of the data move, a cutover window outside business hours, and verification that every workstation opens real case files before anyone starts billing on Monday. The old server stays intact and powered down until the firm signs off.

Do you work with firms outside Sudbury?

Yes. Litigation firms across Northern Ontario and further south work with us remotely for Primafact environments, with on-site visits available across Greater Sudbury, North Bay, Espanola, Elliot Lake, Sault Ste. Marie, and the surrounding region.

Case studies

Related real-world projects

Let's talk about your environment

Free 30-minute consultation. Serving Greater Sudbury, Northern Ontario, and surrounding communities. Remote support available throughout Ontario.

Internal links

Related services, locations, and resources

Related services

Helpful resources

Resources

Latest IT Insights

Cybersecurity guides, Microsoft 365 tips, and managed IT advice from our Ontario team.

Browse all resources