Kinabase Logo
Help & Support

Importing & Exporting Data

Managing data transfers


Kinabase gives you flexible ways to bring data in (Import

) or take it out (Export ) - useful for migrating from spreadsheets, creating backups, or working alongside external systems.

Import and export in Kinabase is CSV only - there's no Excel (.xlsx) support.

You can manage imports and exports from Settings → System → Import / Export, or from within individual collections.


1. Accessing import and export tools

Method A: Via Settings

  1. Click your name in the bottom-left corner and select Settings.
  2. Go to Settings → System → Import / Export.
  3. Select an action:
    • Import: Records, Activities, Tasks, or Data structure.
    • Export: Everything, or individual items like records, tasks, or data structure.

Only System admins have access to this page by default. Admins can grant additional permissions in Settings → Organisation → Users.

Method B: Directly from a collection

  1. Open the collection you want, using the sidebar.
  2. Click the options menu (⋯) in the top-right.
  3. Select Import (.csv) or Export (.csv) for record-based data.

This is handy for simpler tasks, or when you're only working with a single collection.

Method C: From a linked list table

You can also import or export rows directly from a Collection List

on a parent record's detail tab - for example, line items on an invoice, or tasks on a project.

  1. Open a record that has a linked list table.
  2. On the table's label row, click the options menu (⋯).
    • Select Import (.csv) to upload a CSV file.
    • Select Export (.csv) to download the list.
  3. If the table is empty, an inline Import (.csv) button appears next to the Add button.

Every imported row is linked to the parent record automatically - the parent field is hidden from the field-mapping step, so there's no risk of pointing rows at the wrong parent. Exports only include rows belonging to the parent record you're viewing.


2. Importing data

You can import records, activities, tasks, or a data structure.

Dates and times

Kinabase accepts ISO timestamps with fractions of a second (1-7 digits) and a Z or numeric time zone, such as 2024-10-28T23:59:59.4Z or 2024-10-28T18:59:59-05:00. This applies when importing records, activities and tasks.

What is stored depends on the field:

  • Date, Month and Year fields keep the day, month or year written in the file - a late time or a time zone doesn't move it to the next day.
  • Date + Time fields use the time zone in the file and keep the time to the minute.
  • An activity's Timestamp is kept to the second. Fractions of a second aren't stored.
  • Task dates, and an activity's Created At and Updated At, are kept to the minute.

Phone numbers

A Phone Number cell can include its dialling code, for example +33 6 12 34 56 78 or 0033 6 12 34 56 78, and Kinabase keeps it. A local number with no code takes the field's Default Dialling Code or, if that's blank, your organisation's code.

A blank cell doesn't store a number, and on an update it doesn't replace a number that's already saved. See Set a default dialling code.

Durations

A Duration cell must come to a whole number of the field's unit. Larger units in the same family convert exactly, so 2 weeks in a days field is stored as 14 days, and 2.5 hours in a minutes field as 150 minutes. Months, quarters and years don't convert to weeks or smaller, because a month has no set length. A row that doesn't fit is refused, and the import result names the row and the value.

2.1 Importing records

1. Prepare your CSV

Make sure your CSV columns match the fields in your collection (for example, Name, Email, Status). For updating existing records, include an ID or another unique identifier column.

2. Start the import

Go to Settings → System → Import / Export → Import → Records, or open the collection's options menu (⋯) and select Import (.csv).

3. Map fields

Select your CSV file, then on Assign Fields match each CSV column to a Kinabase field. Headings from older exports, such as Address (City), still match. Leave a plain text column, such as Notes » Plain text, on Ignore - it isn't imported. See 3.3 How CSV columns are named.

4. Choose an import type

Select Create new records, or select Update matching records and specify a key field to update existing records without creating duplicates.

5. Confirm

Click Next to run the import.

2.2 Importing record change history

This is similar to importing records, but it also imports historical timestamps for field changes - available to System admins only.

1. Prepare your CSV

Match your columns to the fields in your collection, and include a Timestamp column formatted as dd/mm/yyyy hh:mm:ss.

2. Start the import

Open the collection's options menu (⋯) and select Import (.csv), or go to Settings → System → Import / Export → Import → Records.

3. Choose your import type

Select Import historical values for matching records, then choose the CSV column and collection field to match on.

4. Map fields

Match each remaining CSV column to a Kinabase field.

5. Confirm

Click Next. You'll see historical changes to the imported field values in each record's Activity timeline once it completes.

2.3 Importing activities or tasks

  • Activities: notes, emails, calls, or system updates logged against records.
  • Tasks: action items linked to records, with columns like Task Name, Description or Due Date.

1. Open Import in Settings

Go to Import → Activities or Import → Tasks.

2. Select your CSV

Drag and drop your file, or browse for it.

3. Map required columns

For activities, map columns like Linked Record, Activity Type and Created By. For tasks, map columns like Task Status, Due Date and Assignees.

4. Confirm

Click Next to run the import.

Importing tasks from a previous system helps you keep continuity for due dates, owners and completion history.

2.4 Importing data structures

If you have a .kinabase file - exported from another Kinabase organisation, or provided by our support team:

  1. Go to Import / Export → Import → Data structure.
  2. Select the file and confirm. This creates a new collection, or updates an existing one, based on the structure in the file.

A collection in the file with » in a field name is skipped, and the reason is listed. The rest of the file still imports.


3. Exporting data

A Duration column is exported as the stored amount and its unit, such as 1560 minutes, rather than the shortened label shown on the record.

3.1 Exporting via Settings

  1. Go to Import / Export in Settings.
  2. Choose an export option:
    • Everything - a zip of all records, tasks, activities and data structures (System admins only).
    • Records / Activities / Tasks - each item type as a separate CSV.
    • Data structure - a .kinabase file for your collections, useful for transferring your setup to another Kinabase organisation.
    • Headers only - just the column headers, for building an import template.
  3. Save the file locally.

3.2 Exporting directly from a collection

  1. Open the collection you want, using the sidebar.
  2. Select the options menu (⋯) → Export (.csv).
  3. Name the file, choose where to save it, and confirm.

When this is handy: for quick backups, or analysis in a spreadsheet tool.

3.3 How CSV columns are named

Most fields export as a single column headed with the field name. Some fill more than one column - an address splits into parts such as City and Postcode, a measurement includes its unit, and a Lookup Field

brings across the field it shows. Each extra column is headed with the field name, then », then the part it holds:

  • Address » City
  • Notes » Plain text - a Rich Text field's plain text copy. See Export rich text as plain text.
  • Customer » Address » City - a lookup chains the names.

Collections, collection lists, the Colleagues list, Settings → System → Import / Export and portal pages all use the same headings.

On import, Assign Fields matches both these headings and the bracket headings older exports used, such as Address (City). Field names can't contain », so a field never clashes with an export heading. A name that already contains it is kept until you rename the field.

3.4 How often you can export

Each signed-in person can export up to 10 times every 5 minutes, from a collection or from Settings → System → Import / Export. The allowance is your own, so a colleague exporting at the same time doesn't use it up. Exports you run with View as user count against your allowance.

If you reach the limit, Kinabase asks you to try again later. Wait a few minutes and export again.

Portal users have their own allowance. See Portal security.


4. External backups

Available on the Max plan.

On the Max plan, you can schedule a nightly external backup that delivers a complete workspace archive - records, activities, tasks and workspace setup, packaged as a single zip - to an external storage library you control.

1. Connect a storage library

Make sure at least one external storage library is connected under File Storage settings.

2. Open External Backups

Go to Settings → System → Import / Export and find the External Backups panel.

3. Configure the schedule

Click Configure, turn on Enable daily backups, and choose a Backup destination from your connected storage libraries.

4. Choose a retention period

Select 7, 14, 30, 60, 90 or 365 days, or Retain forever. Older archives are cleaned up automatically once they fall outside this window.

5. Save

Backups run nightly at 02:00 UTC. Use Run backup now at any time - for example, before a major configuration change - and View recent runs to check status or open an archive in your storage library.

External backups complement Kinabase's standard platform backups - they give you an independent copy of your data, in storage you own.


5. Troubleshooting imports

  • Before updating existing records, export a CSV as a backup in case something overwrites incorrectly.
  • Keep an eye on the import result to confirm it succeeded.
  • If your CSV is large, consider splitting it into smaller chunks.

Handling failed imports

Failed import prompt

If any rows can't be imported, Kinabase prompts you to re-download a CSV containing only the problem rows.

Include errors column

Tick Include Errors Column. This adds a column describing why each row failed, such as an invalid field value.

Example

If 'Botswana' doesn't exist in your 'Countries' collection, the error might read 'Value not found in linked field.'

Solution

Either fix the row - change 'Botswana' to an accepted value - or add a 'Botswana' record to your 'Countries' collection, then re-import.

Avoiding duplicate records

In the Assign Fields step, tick Skip duplicate records to avoid reimporting rows that already succeeded on a previous attempt.

Still having issues?

Check you have the right import permissions under Settings → Organisation → Users. If problems persist, contact our support team.


Need more help? Ask your System admin, or contact our support team via Help & Support.