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

Where does a row in Excel go?

Choose clients, cases, invoices or time entries, map CSV/XLSX columns and review the preview. Valid rows are processed in the background after your explicit approval; inspect the final results too. Exports depend on permissions and record scope. Backup and restore arrangements need confirmation before service.

Excel · clients.xlsx

Excel · clients.xlsx
ABC
1Full namePhoneIdentifier
2Client A0532 000 00 01Example field
3Client B0532 000 00 02Example field
4Client C0532 000 00 03Example field

Illustrative client fields

Client name
Client A
Phone
0532 000 00 01
Identifier
Example field
Status
Illustrative view

01/04

Choose one target and map columns explicitly

Each job has one target. Exact field keys in a template can map automatically; you choose mappings for other headings. Required and duplicate mappings are validated. Requested case-type, status or related-record IDs must be valid and accessible; names are not assumed to resolve automatically to IDs.

An assistant marking a column on a printed spreadsheet beside an old archive box
Moving from Excel
Fields from different targets; not one file or a complete required-field list
Excel columnSample valueVekilaw fieldModule
fullNameClient AfullNameClient
phoneNumber0532 000 00 01phoneNumberClient
email[email protected]emailClient
caseNumber2026/42 E.caseNumberCase
caseTypeIdExisting type IDcaseTypeIdCase
courtNameCourt of First Instance (civil)courtNameCase

02/04

Prepare, preview and explicitly approve

The illustrative animation shows preparation/mapping/preview only; it uploads no file and creates no record. The real screen checks target, branch, required fields and job revision; writing needs separate approval.

  1. 01/03

    Use a header row. Download the current CSV/XLSX template for the target; a file may contain at most 5 MiB and 5000 data rows. Clients, cases, invoices and time entries are separate job targets.

  2. 02/03

    Map columns to the selected target’s fields. Clients and cases are different targets; required fields and existing-record IDs depend on that target. The example shows only some fields.

  3. 03/03

    Preview creates no actual records. Review invalid rows and reason codes; only valid rows enter the queue after explicit approval. Permissions, references or duplicate-record state may change during processing; check final outcomes and the error report too. Cancellation does not undo records already written.

If a file does not match a supported target/template, assess its scope first; not every old-system export can be imported directly. Confirm any migration support separately. The spreadsheet migration guide describes preparation.

Prepare

03/04

Transfer, archive and backup are different operations

  • Backup conditions

    Hosting location, backup frequency, retention, access and restore drills for Vekilaw need confirmation before service. This page is not evidence of an executed backup or measured recovery time; an export file is not an automatic restore system.

  • Export

    Client, case, invoice, time-entry and document-metadata lists support CSV/XLSX. The relevant read permission plus export permission and current company/case/branch scope are required. Search and sorting apply; the limit is 50 000 rows, so narrow filters if exceeded. Document-list export has no file contents; company archives use a separate authorized workflow.

  • Erasure request

    An authorized user records/reviews a data-subject request and performs the scoped package/erasure workflow. Legal retention and deferred legacy/AI person-matching policies prevent an automatic complete-erasure promise. Consider the KVKK guide and security and KVKK page with legal approval.

04/04

What do people ask about data migration?

  1. 01/06

    Which formats can be imported?

    CSV and XLSX for clients, cases, invoices and time entries. Import requires permission to manage imports, the target create permission, a writable company and an accessible branch. Files must fit 5 MiB and 5000 rows; old-system exports must be adapted to the target template.

  2. 02/06

    What happens to faulty rows?

    Invalid preview rows are excluded from approval. Rows that preview as valid still face processing-time rules; inspect final job and row outcomes. Error reports contain row/field/reason information, not copies of uploaded cell contents. Reuploading the same invalid file is not a correction; cancellation does not delete written records.

  3. 03/06

    In which format can I export?

    Five lists support CSV or XLSX: clients, cases, invoices, time entries and document metadata. Both read permission and export permission are required, with scope/filters and a 50 000-row limit. Document file contents are excluded. Company archives and restore are separate processes.

  4. 04/06

    How is an erasure request processed?

    A request is recorded and an authorized user reviews scope and retention. Supported records have package and erasure/anonymization workflows; do not assume all historical free text and raw-address records are automatically cleaned. Deferred policies and legal retention approval must be completed. See the KVKK guide.

  5. 05/06

    How do I restore from a backup?

    Backup frequency, retention and restore-drill results require separate confirmation. Scope and support are planned under the service agreement; this page promises no proven backup, fixed recovery time or self-service restore control.

  6. 06/06

    What if my old program offers no export?

    First assess the available format, data scope and authorized transfer method. No ready-made connector or guaranteed migration service is promised for every old system. Contact us to discuss scope.

Confirm the template and transfer scope first.