Bringing existing notes into NoteGate

With launch partners live, every new shift note and progress report is authored inside NoteGate's compliant note-taking workflow from the first keystroke and lands in your CRM compliant. This page covers historical notes already in your CRM that you want to bring into NoteGate's audit and validation history.

What NoteGate does NOT migrate: rosters, billing records, participant clinical histories, care plans, or any other CRM data. NoteGate is the compliance authoring layer. Your CRM remains the system of record for participant management. Migration here refers only to historical shift notes and progress reports you want in NoteGate's audit trail.

Three ways to bring notes in

1

CSV import

Download the per-CRM CSV template for your platform, export your notes into the required columns, and upload via the admin dashboard. Templates are available below for Lumary, VisualCare, ShiftCare, FlowLogic, and a generic format. Available today.

2

API bulk import Q2 2026

The API bulk import endpoint (POST /v1/notes/bulk) is planned for Q2 2026. Until then, CSV import is the recommended path for large historical archives.

3

Vendor-assisted migration

For large historical archives, complex custom fields, or high-volume imports that exceed CSV tooling, NoteGate offers a fixed-fee assisted migration engagement. Scoped after a 30-minute technical discovery call. Email api@notegate.com.au.

Download the template for your CRM

Each template contains the canonical column headers NoteGate expects, with two example rows to illustrate the expected format. Columns marked required must be populated. Optional columns can be left blank.

Lumary (Salesforce)

Maps Lumary Case Notes report export columns including Salesforce __c custom fields to NoteGate canonical schema.

Download CSV

VisualCare

Maps VisualCare client note export columns including appointment_date, carer_id, and care_note_text fields.

Download CSV

ShiftCare

Maps ShiftCare Event Details Report CSV export columns including carer_id, client_name, and note_content fields.

Download CSV

FlowLogic

Maps FlowLogic progress note export columns including POWS terminology (pows_id, support_worker_id, progress_note).

Download CSV

Generic format

Use for any CRM not listed above. Maps directly to NoteGate's canonical schema. Required columns listed in the header row.

Download CSV
API bulk import (POST /v1/notes/bulk) is planned for Q2 2026. For large imports before then, use CSV or contact us for vendor-assisted migration.

Before you import

Migration readiness checklist

Define the data scope: which participants, which date range, which note types (shift notes only, or progress reports too).
Export notes from your CRM in the format matching your chosen template (CSV export or report export).
Map your CRM's field names to the template columns. Use the custom field mapping admin endpoint if your instance uses non-standard field names.
Review 5 to 10 sample rows manually before importing the full set to catch mapping errors early.
Confirm historical notes will be imported as read-only compliance records, not as new authoring sessions.
Get sign-off from your compliance manager or supervisor before importing historical records.

What NoteGate does not migrate

  • Participant profiles, care plans, or clinical histories
  • Rosters, shift schedules, or payroll records
  • Billing records or NDIS claim history
  • Incident reports created outside NoteGate (use NoteGate IRA for new incidents going forward)
  • Any data that is not a shift note or progress report

Your CRM remains the system of record for all of the above. NoteGate is the compliance authoring layer. The migration here brings historical notes into NoteGate's audit trail only.

Vendor-assisted migration

For providers with large historical archives (thousands of notes), complex custom fields, or data that does not fit the standard CSV templates, NoteGate offers a fixed-fee vendor-assisted migration engagement.

The engagement is scoped after a 30-minute technical discovery call. We will confirm the data scope, the field mapping approach, and the import timeline before any work begins.

Request a migration discovery call →