Skip to main content
Vekilaw logo: Hukuk Bilgi İletişim Sistemi (legal information and communication system)

By Vekilaw Editorial Team

Updated:

9 min read

Excel column

B · Full name

Vekilaw field

Client: fullName

How does a spreadsheet become records?

Check source data, permissions and relationships when moving from spreadsheets. Each import job handles one record kind and runs in the background after preview and confirmation.

From Excel to legal software: migrating records to a new system

Law firm assistant moving records from an old spreadsheet into a new case management system at a two-monitor desk, archive boxes beside the desk

01/11

How does an Excel file turn into records?

Illustrative client import: identifiers are masked and only three columns are shown. The current template contains all required fields, including type, email and phone. This is not a working form or a real job outcome.

  1. 01/05

    Select CSV/XLSX and Clients. Uploading does not create client records.

  2. 02/05

    Validate required fields and the branch; map only the selected record kind.

  3. 03/05

    The illustration has three eligible rows and one invalid row. Identity validation checks more than length.

  4. 04/05

    The invalid row stays excluded; confirm three eligible rows against the current preview revision. Correct the source file and try a new job if needed.

  5. 05/05

    This illustrative background job creates three clients; one source row was not imported. No cases, hearings or parties are created.

Choose a client file

02/11

Column mapping: which field does each column go to?

Choose Clients, Cases, Invoices or TimeEntries for a CSV or XLSX file. A job maps only that kind’s fields; required template columns and accessible branch/catalog references must be valid.

Start with a small file. Review preview errors, explicitly confirm eligible rows, then wait for background processing and row outcomes. Correct source cells in your own file and upload/preview again.

Excel column

Vekilaw field / Note

AClient type and name

Clients: clientType, fullName

Use Individual/Corporate type codes

BTCKN or VKN

Clients: identifier

Length/checksum required; branch duplicates may be rejected

CEmail and phone

Clients: email, phoneNumber

Separate required fields

DCase number, court, type, status, city, description

Cases import

All six are required; check catalog values in the template

EInvoices and time entries

Separate import kinds

Each has its own required fields and existing-record references

FOpposing parties, hearings and deadlines

Not fields of this import template

Add and verify separately through the relevant case screens

GCase notes or documents

Not created by this import job

Save later through the relevant screens

03/11

Where does spreadsheet case tracking break down?

Excel can support collaboration and access settings. As a firm grows, coordinating spreadsheets with cases, documents and permissions may become harder. Base migration on your actual workflow.

Below are six common limits and what each looks like in dedicated software.

Before: Excel and folders

  • Without configured collaboration or version tracking, edits may conflict.
  • Poorly scoped file sharing may expose more rows than needed.
  • Date cells need a separate reminder workflow.
  • Clients, cases and documents live in different files and you link them by hand.
  • Search only works in the open workbook and old years disappear into folders.
  • The sheet travels by email and nobody knows how many copies exist.

After: Vekilaw

  • Company records are read through your current access scope; refresh screens when needed.
  • Roles and permissions decide who sees what.
  • Deadlines are recorded separately in case context; calendar visibility and reminder delivery depend on permissions, settings and channel conditions.
  • Clients, cases and documents are linked records.
  • Search covers supported record metadata within company, branch and case access; it is not document-content OCR search.
  • Accounts and permissions control access; sharing exported copies needs separate management.

Track who receives source and exported files containing client information. Assessing personal-data security (opens in a new tab) involves sharing, access and retention processes as well as software.

04/11

Preparation: decide what to move

The costliest mistake in a migration is trying to move everything. Start by deciding which files are live: pending cases, open deadlines and active clients. Make a separate archive decision for closed files.

Take an inventory: how many spreadsheets exist, who owns each, which columns are used and who edits them. Files where the same client appears under three spellings become visible at this stage.

Before: Excel and folders

  • Files are scattered across personal computers and inboxes.
  • Only the person who built a sheet knows what its columns mean.
  • It is unclear which workbook is the current one.

After: Vekilaw

  • The live files to move are listed.
  • Every column has a target field.
  • One workbook is marked as the source of truth.

Do this in this step

  • Write down the number of pending cases and open deadlines.
  • Record the owners and last update dates of the source workbooks.
  • Decide where closed files that will not be moved are archived.
  • Appoint a migration lead and a pilot team.

05/11

Data cleaning: fix it before you import

Cleaning is the most tedious and the most valuable step. Wrong data moved into a new system is just wrong data in a tidier place. Pick one format for each column and correct it in the source workbook.

Check dates, case-number formats, phone numbers and TCKN/VKN checksums. Do not merge apparent duplicates by name alone; have an authorized person verify identity and relationships.

Before: Excel and folders

  • Dates are text; some are day.month, others month/day.
  • The same client repeats under several spellings.
  • Case numbers are free text.
  • There are empty and merged cells.

After: Vekilaw

  • Date fields have been checked against the selected schema; calendar records are verified separately.
  • Duplicate candidates have been reviewed; rows sharing an identifier are not automatically merged.
  • Court and case number are separate fields.
  • Every row is one record.

Do this in this step

  • Use the rule of one row per case and one row per client.
  • Check identifier checksums as well as length, and use the selected kind’s template to check mandatory phone and email fields.
  • Convert date columns from text to a real date format.
  • Make corrections in a copy of the source file and keep the original.

06/11

Verification after the import: check the numbers

Compare source, preview and outcome totals: valid, invalid, succeeded and failed rows. Processing confirmed rows may partly fail; a completed job does not mean every source value migrated. Check hearings, deadlines, parties, notes and documents separately.

Compare selected records with the source. Review dates, missing required fields and references. Verify deadlines, hearings and party links added outside import separately; file import does not build them automatically.

Before: Excel and folders

  • Whether the import is correct depends on who you ask.
  • An error only surfaces when a hearing is missed.

After: Vekilaw

  • Counts are compared one to one with the source workbook.
  • Sample files are verified one by one and differences are recorded.

Do this in this step

  • Note the row counts in the source workbook before importing.
  • Print the open deadlines and the next thirty days of hearings as a list and compare.
  • Correct differences in the source and re-import with the same mapping.
  • Write the name of the person who verified, and the date, in a note.

07/11

Pilot period: one team, a limited number of files

Instead of moving the whole firm overnight, work for two weeks with one team and around twenty live files. The pilot exists to find mapping errors and the views your team needs at a small risk.

During the pilot keep Excel read-only and make every update only in the new system. Updating in two places at once is the most common reason a migration fails.

Before: Excel and folders

  • Updates are made in two places at once.
  • People argue about which record is right.

After: Vekilaw

  • The pilot team updates only the new system.
  • Excel is a read-only reference and differences are listed.

Do this in this step

  • Write success criteria in advance: are all open deadlines in the new system, is the hearing calendar correct?
  • At the end of the pilot, fix mapping errors and move on to the full import.
  • Include both a lawyer and an assistant in the pilot so different roles' views get tested.

08/11

Team training: by role and short

Training should retell the daily work, not tour the features. Show assistants how to open a case, enter deadlines and hearings and upload documents; lawyers the case view, agenda and notifications; partners and managers reporting and access management.

Define roles and permissions before training. If people only see the screens for their own work when they log in, training takes less time. If the team will draft with AI, add the guide to AI drafting for lawyers to the training plan for its safe-use rules.

Before: Excel and folders

  • Everyone uses the same sheet in their own way.
  • A newcomer learns the sheet from the veterans.

After: Vekilaw

  • Each role starts with screens suited to its work.
  • A newcomer starts working on day one with a defined role.

Do this in this step

  • Plan a thirty to forty-five minute session per role using a real file.
  • Collect frequently asked questions in one shared note.
  • In the first week hold a ten-minute Q and A at the end of each day.

09/11

Retiring Excel and retention

Create an access-controlled retention plan for old spreadsheets and documents. Have a qualified professional assess sources such as Attorneyship Law Article 39 (opens in a new tab), personal-data legislation (opens in a new tab) and professional rules (opens in a new tab) for your files; do not apply one period to every record kind.

This guide sets no retention period or erasure decision. Your firm must separately manage access, backups and disposal for unimported or exported copies.

Do this in this step

  • Move the final version of each old workbook to one date-stamped archive folder.
  • Restrict access to the archive folder to the partners.
  • Write down the deletion date for anything whose retention period has ended.

10/11

The first 30 days

Split the first month into four weeks, each with a single goal. Do not move on before the goal of the week is met.

  1. 01/04

    Week 1: Preparation and cleaning

    Inventory, list of live files, data cleaning and role definitions. Stop entering new records in Excel at the end of the week.

  2. 02/04

    Week 2: Pilot

    Pilot supported record kinds, check mappings and outcomes, and separately enter and verify deadlines and hearings.

  3. 03/04

    Week 3: Full import and training

    Import of all live files with the corrected mapping, plus role-based training sessions.

  4. 04/04

    Week 4: One system

    Excel becomes a read-only archive, deadline and hearing tracking runs from the new system, and the first feedback meeting is held.

11/11

Frequently asked questions

  1. 01

    How long does a move from Excel take?

    It depends on the number of files and the quality of the data. The plan in this guide targets the first month for live files; data cleaning is what drives the time most.

  2. 02

    Should I move closed historical files too?

    Define scope for active records first. Moving or retaining older files depends on data kind and your retention policy; do not assume these templates import every old file.

  3. 03

    How do I add documents and notes that are not in Excel?

    Upload documents through the document screen and save case notes in case details. These steps are separate from import; linking a document to a case is optional and a direct client link is not implied.

  4. 04

    Is the imported client data safe?

    Records are kept in a separate scope for your firm and protected by roles and permissions. The security page describes the technical measures in detail.

Official sources

The provisions on migration and retention cited here were read from the Legislation Information System and Turkish Bar Association sources on 6 October 2026.

  1. 01Attorneys' Law No. 1136 (opens in a new tab): art. 39
  2. 02Personal Data Protection Law No. 6698 (KVKK) (opens in a new tab): arts. 4 and 12
  3. 03Turkish Bar Association Professional Rules (opens in a new tab): art. 37

Try a controlled migration with a small file first.

Free trial · no card