Migrate to AccessPoint

Yes — along with your assessments, incidents, complaints, requestor directory, register-level risks, and vendor register. Settings → Data import & export generates an Excel template pre-filled with your tenant's own type codes and stage values; you fill one row per record, upload, and read a per-row validation report before anything imports. Historical requests keep their original identifiers as legacy references, and legacy case files migrate through a staging container in your own tenant's Azure storage.

Both, in the same pass. The import carries each case's status and stage, its key dates including the due date, and its responsive documents — so an open request arrives mid-stride, exactly where it stood, and your team continues it in AccessPoint. That means no cutover day: you don't freeze intake, run two systems in parallel, or wait for the old caseload to close out. And because the old file numbers persist as searchable legacy references, correspondence that arrives quoting them still finds the right case instantly.

No. The whole path is a spreadsheet exercise: any report or export from your old system that reaches Excel is enough as source material, the import template's dropdowns already carry your configured codes, and validation happens in the panel with a fix-and-reupload error workbook. Most offices run their own migration; if you'd rather have it done with you, migration and onboarding services are available.

Arrival is deliberately quiet: no notifications are sent, no reviews spawn, and nothing recomputes — the dates you supply are stored exactly as given, since a migrated determination is a record, not something AccessPoint second-guesses. For an in-progress case that means the due date you import is the due date your team sees, and the file continues from there. Every imported record carries an Imported audit-trail entry, so provenance stays visible forever.

Through the pre-provisioned migration-staging container in your own tenant's Azure storage account — nothing to provision, it ships with the deployment template. Stage files folder-per-case with AzCopy for volume (or drag-and-drop for smaller sets), list each file on the workbook's Documents tab, and optionally include an MD5 content hash: when both the manifest and the staged file carry one, the importer verifies them and rejects a mismatch — an optional chain-of-custody check. Imported files ride the same conversion and indexing pipeline as native uploads, and staged files auto-delete after 60 days so sensitive records never linger outside the document lifecycle.

Your old identifiers always come along in the Legacy reference column, searchable forever. By default AccessPoint generates fresh IMP-prefixed numbers so it stays the single numbering authority — but if your register or a published disclosure log requires the old number to remain official, supply it and it's kept verbatim. A supplied number that matches your configured numbering format even advances the sequence, so newly created cases continue cleanly after it.

Always. Uploading a workbook imports nothing by itself — it produces a validation report showing what would be created, skipped, or rejected, per tab. Imports are strictly create-only: a row matching an existing case is skipped without touching that record. Download the error report to get your own workbook back with an Errors column appended, fix, and re-upload as many times as it takes.

Then the same panel works in reverse — and that's the point. The Export tab produces a business-readable Excel workbook of your requests, assessments, incidents, complaints, requestors, risks, and vendors any time you want one, and because the database and documents live in your own tenant, standard Azure tooling works against them with no vendor involvement. The exit being easy is exactly why the entrance is safe.