Comparison & migration guide

AccessPoint vs. AccessPro — and what to do now that AccessPro is legacy

AccessPro Case Management ran Canadian ATIP offices for two decades. It's now formally a legacy application, and every institution still on it needs a destination. Here's an honest comparison — and the practical path for bringing your history with you.

Request a Demo Explore AccessPoint

The short answer

AccessPro is an on-premises ATIP request tracker from the mid-2000s that the Treasury Board of Canada Secretariat declared a legacy application effective June 2023 — institutions still running it are actively migrating off. If you're choosing its successor, the real question isn't which request tracker to buy next: it's whether your next system should also carry the privacy side of your mandate (PIAs, AIAs, breaches, complaints, risk) and whether your data should live in a vendor's cloud or your own Microsoft 365 tenant. AccessPoint is built on the second answer to both.

What is AccessPro Case Management (APCM)?

AccessPro Case Management — often shortened to APCM — was built by Privasoft Corp. of Ottawa and became the standard ATIP processing system across much of the Government of Canada, alongside its AccessPro Redaction companion. Privasoft was acquired by CSDC Systems in 2011, CSDC rebranded as Calytera in 2019, and Calytera was acquired by Granicus in 2020 — so AccessPro ended up under the same owner as the AMANDA platform.

Its retirement has been unusually public. The City of Toronto reported in 2018 that support and licensing for its version of AccessPro would be discontinued, forcing a sole-source upgrade. Federally, TBS notified departments in late 2021 that APCM would become a legacy application effective June 2023, triggering a government-wide replacement effort; departmental ATIP annual reports (Correctional Service Canada, the Public Service Commission, CIRNAC and others) describe migrations to a successor system, with some institutions still processing on AccessPro mid-transition.

None of this is a knock on the offices that ran it well for twenty years. But if your institution is one of the ones still on APCM, the migration is no longer optional — the only open question is what you migrate to, and how much of your mandate the next platform carries.

AccessPro and AccessPoint, side by side

AccessPro AccessPoint
Scope ATIP/FOI request processing and redaction Access requests plus PIAs, AIAs, breach response, complaints, and a privacy risk register — one platform
Where your data lives On-premises servers you maintain Your own Microsoft 365 and Azure tenant — cloud, but still yours
Product status Legacy application (GC designation effective June 2023) Actively developed, with a public roadmap
Records collection Documents imported into a separate system Pulled straight from SharePoint, OneDrive, Outlook, and Teams
Redaction AccessPro Redaction desktop companion Browser-native redaction studio with statutory exemption tagging and AI-proposed redactions
Jurisdiction rules Configured per deployment 106 jurisdiction packs — deadlines, exemptions, calendars, letters, report templates
Audit trail Application logging Hash-chained, append-only ledger with court-ready case audit exports
Pricing Licensed per deployment; quotes Flat annual, published on the site, no per-user fees

Competitor capabilities vary by product edition and configuration; this table reflects each product's public positioning as of August 2026.

Where AccessPro fits

A fair comparison cuts both ways — AccessPro is a reasonable choice when:

  • You're mid-migration on a TBS-coordinated replacement path and the successor has already been procured for your institution.
  • Your office needs to keep processing on APCM through the transition — it still works, and an orderly migration beats a rushed one.
  • Your requirements genuinely stop at access requests and your IT strategy accepts running or hosting a separate case system.

Where AccessPoint differs

Your tenant, not another silo AccessPoint deploys into the Microsoft 365 and Azure environment you already run — no new servers to host, no vendor cloud to assess, and records collect straight from where they already live.
The whole mandate, not just requests The same offices that process access requests run PIAs, breach responses, and complaints. AccessPoint runs all of it on one audit ledger instead of leaving the privacy side in Word templates.
No forced migrations, ever again AccessPro's retirement forced this decision on you. AccessPoint's answer is structural: your data sits in your own database with a one-click business-readable export — leaving is always possible, which is exactly why you can trust staying.
Statute-aware from day one Jurisdiction packs preload ATIA/provincial deadlines, exemptions, business-day calendars, and statutory report templates — the rules APCM deployments carried as years of local configuration.

Migrating from AccessPro to AccessPoint

AccessPro offices hold years of case history, and it should come with you. AccessPoint's Data import & export panel is designed for exactly this move — no ETL project, no developer.

  1. Get your history into Excel. Any APCM report or export that reaches a spreadsheet is enough — you don't need a database extract or vendor engagement.
  2. Download AccessPoint's import template from Settings → Data import & export. It's generated for your tenant, so its dropdowns already carry your configured request types, stages, and codes; keep your old case numbers in the Legacy reference column.
  3. Upload and validate. You get a per-row report — created, skipped, errors — before anything imports, with a fix-and-reupload error workbook. Re-runs are always safe because imports are create-only.
  4. Stage legacy documents in the pre-provisioned migration-staging container in your own Azure storage (AzCopy for volume), list them on the Documents tab, and optionally verify hashes for chain of custody.
  5. Import. Records arrive historical by construction — no notifications fire, no deadlines recompute, and every record carries an Imported audit-trail entry.

Rehearse first if you like: the Export tab produces the same workbook the importer accepts, so a trial run against a test tenant validates cleanly before you touch production.

Plan your migration →  ·  Data Import & Export guide  ·  Migration & onboarding services

Questions people ask about AccessPro and AccessPoint

Is AccessPro end of life?
For the Government of Canada, effectively yes: the Treasury Board of Canada Secretariat notified departments in late 2021 that AccessPro Case Management would become a legacy application effective June 2023, and departmental ATIP annual reports since then describe active migrations to successor systems. Some institutions are still processing on it mid-transition, but it is a system to migrate from, not to.

What replaces AccessPro?
The TBS-coordinated federal replacement effort has seen institutions procure ATIPXpress, a cloud ATIP request tracker. But a replacement decision is also a scope decision: if your office runs PIAs, breach responses, complaints, and privacy risk alongside access requests, AccessPoint replaces AccessPro and the spreadsheets around it — in your own Microsoft 365 tenant rather than a vendor's cloud.

Can we import our AccessPro history into AccessPoint?
Yes. Any AccessPro report that reaches Excel can be mapped into AccessPoint's tenant-generated import template — historical requests keep their old case numbers as legacy references, requestor contacts import alongside them, and legacy documents stage through your own Azure storage with optional hash verification. Imported records arrive inert: no notifications, no recomputed deadlines, full audit provenance.

How is AccessPoint different from AccessPro?
Three structural differences. Scope: AccessPro processes access requests; AccessPoint runs access requests plus privacy and algorithmic impact assessments, breach notification, complaints, and a privacy risk register on one shared audit ledger. Architecture: AccessPro is on-premises client-server software; AccessPoint is Microsoft 365-native and deploys into your own tenant, collecting records straight from SharePoint, Outlook, and Teams. And continuity: AccessPro's retirement forced a migration on its customers — AccessPoint's one-click export means you're structurally never locked in.

We're still on AccessPro mid-migration. How long can we take?
That's between your institution and its support arrangements — several federal ATIP annual reports show offices still processing on APCM while their successor deployment completes. The practical advice: whatever destination you choose, do a rehearsal import of a year of history early. It converts migration from a scary unknown into a checklist, and AccessPoint's validation workbook is built to make that rehearsal a one-afternoon exercise.

Competitor information on this page is drawn from public sources — vendor websites, government reports, and press coverage — and was last reviewed in August 2026. Products evolve, and a comparison is never the whole story: capabilities vary by edition and configuration. Spot something out of date? Tell us and we'll correct it.

Leaving AccessPro? Land Somewhere You Own.

Try AccessPoint free for 30 days in your own Microsoft 365 tenant — and rehearse your migration before you commit.

Start Free Trial