Coal Road Migration Guide

Draft for business use; independent legal review recommended. Migration paths vary by source platform, export/API access, data quality, volume, permissions, and customer requirements. No tested one-click Clio, Needles, or other connector is claimed here.

1. Export & Map

Inspect the source platform, available exports/APIs, data dictionary, and customer access. Map matters/clients, contacts, documents, users, permissions, calendar data, billing records, and other agreed records. Identify unsupported formats, missing relationships, duplicates, and confidential-data handling requirements.

2. Import & Validate

Load an authorized sample or full dataset into a controlled environment. Compare record counts and relationships. Review representative matters, documents, users, permissions, financial records, dates, and agreed samples with the customer. Resolve exceptions before cutover.

3. Cut Over & Verify

Agree a change freeze or delta process, run final migration work, validate user access and representative workflows, and complete an administrator handoff. Keep a written rollback/recovery plan and confirm who authorizes production cutover.

Scope and pricing

Migration assessment, execution, data cleanup, integration work, and cutover support are professional services, separate from software purchase. Unknown data quality, damaged or proprietary sources, substantial historical documents, multiple offices, complex identity/security, on-site work, or scope above the online threshold require a scoped estimate.

Never send production/client data to a development or migration environment without authorization and agreed safeguards.