Check migrated task records from MyCase to Clio Manage
Get the source data and prepare the review

Conditional documented MyCase-to-Clio task acquisition; comparison stops without migration-owner ID crosswalk and coverage

WHAT WAS CHECKED
Official documentation checked; all routes are proposed and have not been run in a product account. No client data, account access, installs or account writes used. Native column names are distinguished from editorial kit contracts. Missing source evidence blocks completeness claims.

BEFORE YOU START
- An actual MyCase-to-Clio Manage migration, limited here to task records; authorized source backup and target task-export access.
- Migration-owner-approved source-task to target-task ID crosswalk, task field mapping, cutoff/timezone, scope and intended changes. Official guides do not establish these account-specific mappings.
- Firm-approved Excel; optional Copilot entitlement and tenant approval for the exact minimized data. Native Excel analysis can be done manually if Copilot is absent.
- Keep raw exports and identifying source pointers in a separate restricted location. The AI workbook contains only approved alias-based tables and visible policy/scope text, never raw client records on another tab.

DATA ACQUISITION LIMITS
- This guide compares task records only. It does not audit documents, invoices, finances, contacts, matter migration or a signed-client handoff.
- Clio documents MyCase task migration and both vendors document relevant exports, but stable source-to-target task identity/field mapping is not guaranteed by those docs. Missing or ambiguous crosswalk blocks comparison.
- A current MyCase backup after later task edits is not necessarily the migration-cutoff source snapshot. Prefer the actual retained cutoff backup; otherwise document and approve every intervening change.

DECLARED INPUT CONTRACT
source.csv: record_type, record_id, matter_alias, owner_alias, start_or_due_datetime, timezone, status
target.csv: record_type, record_id, matter_alias, owner_alias, start_or_due_datetime, timezone, status
id-map.csv: source_id, target_id
intended-changes.csv: record_id, field, approved_old_value, approved_new_value

STEP 1: Collect the real MyCase task snapshot
Tool: MyCase
Open: Settings at bottom of left navigation > Import/Export > Full Backup > Create Backup
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Prefer the actual retained source backup from the migration cutoff. If a new authorized snapshot is needed, select CSV, the approved all-cases or linked-cases scope and Include archived items as required; create the backup, wait for Pending to become Download, then download the ZIP. Inspect its Tasks CSV. Record export time, selected case/archive scope and source task count; keep the other sensitive backup files restricted and out of AI.

Expected output: Native MyCase task CSV from the actual backup, with cutoff/scope/count controls.
Use it next: Have the migration owner verify that this is the source task population actually migrated.
Check: The backup may contain many unrelated record types; this recipe uses Tasks only. Current backup state is not proof of historical cutoff state.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://supportcenter.mycase.com/en/articles/9370346-how-do-i-get-my-data-out-of-mycase
https://help.clio.com/hc/en-150/articles/10263146574107-Migrating-Data-From-Your-Current-Software-G-M

STEP 2: Collect the matching Clio task snapshot
Tool: Clio Manage
Open: Tasks > Outstanding > Filters > Apply filters > bottom Export > CSV > Export; repeat Completed
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Export the migrated task scope from the actual target Clio account. Retain separate Outstanding and Completed files, export time, filters and record counts. Inspect actual task IDs and full descriptions using Expand rows or Print task as needed. Do not import, edit, reassign or mark tasks complete.

Expected output: Actual target task CSVs and coverage controls.
Use it next: Obtain the migration-owner source_id/target_id crosswalk and explicit field mapping before joining.
Check: Do not match tasks by similar names or assume MyCase IDs are preserved in Clio. Private/hidden or excluded tasks remain coverage gaps.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://help.clio.com/hc/en-us/articles/9204982812699-Filter-and-Export-Tasks
https://help.clio.com/hc/en-us/articles/9204917906971-Manage-Tasks-in-Clio-Manage

STEP 3: Map the observed records to the starter input
Tool: Excel and authorized staff
Open: Separate analysis workbook > Home > Format as Table
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Create source.csv and target.csv with record_type fixed to task. Preserve actual record_id and map matter_alias,owner_alias,start_or_due_datetime,timezone,status only using the migration-owner-approved field map; inspect original tasks for unresolved semantics. Obtain id-map.csv source_id/target_id from the actual migration log or an independently verified owner crosswalk. Copy intended-changes.csv from explicit approved changes. Put per-status counts, both capture times, cutoff, case/archive/visibility scope, date precision and exclusions in visible Scope. If stable identity or coverage is absent, stop: do not infer it from similar text. Create named tables Source, Target, IdMap and IntendedChanges in the separate alias-based workbook.

Expected output: Task-only comparison inputs and a verified identity/field crosswalk, or a precise missing-crosswalk/coverage checklist.
Use it next: Check the mapping against each original source before using AI.
Check: Aliases and missing policy fields are staff-created; do not relabel a native export as the kit schema. Unknown stays blank/unknown, not false or zero.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model

STEP 4: Review the bounded evidence with Copilot
Tool: Excel Copilot, optional
Open: Approved analysis workbook > Copilot icon at lower right > Chat only
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

Use Chat only and submit the prompt. Without Copilot: perform exact ID joins after validating mapping uniqueness and record-type controls.

PASTE THIS PROMPT
First verify Scope contains both actual task snapshots, cutoff/coverage/count controls and a migration-owner-approved unique source-to-target ID crosswalk and field mapping. If any is absent or ambiguous, return comparison_blocked and the exact evidence needed; do not infer identity from names/text. Otherwise compare Source and Target through IdMap and IntendedChanges. Return missing/extra tasks, duplicate mappings, owner/status/date differences and explicitly approved changes with row references. Preserve date-only precision and timezone; do not calculate legal deadlines, edit tasks or declare the whole migration successful.

Expected output: A conditional migration exception report, or explicit blocked data requirements.
Use it next: Copy the draft exception list to the reviewer; retain row references.
Check: Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits.
Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises.
Source documentation:
https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel
https://support.microsoft.com/en-us/excel/copilot/frequently-asked-questions-about-copilot-in-excel

STEP 5: Approve the review result
Tool: Responsible staff reviewer
Open: Reviewed local worksheet
Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested.

The migration owner resolves acquisition/mapping gaps and validates task counts and source records, including private/archived and completed/outstanding coverage. Approve only the reviewed task comparison; other migration record types are outside this guide.

Expected output: Blocked-input checklist or reviewed migration exceptions.
Use it next: Any external message, source change, payment or deletion requires its own authorized process.
Check: A successful sample or equal total count cannot establish complete migration fidelity.
Documentation limit: Editorial human-review gate; linked Excel documentation supports the worksheet used, not legal or accounting conclusions.
Source documentation:
https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model

ACCOUNT AND SOURCE CHECKS STILL NEEDED
- Actual source/target task CSV columns, exported IDs, migration crosswalk and completeness counts are account-specific and have not been tested.
- MyCase backup creation is limited to one per day; retain the actual downloaded ZIP and use the correct cutoff snapshot.

USING THE FILES IN THIS KIT
Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs.

The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.
