> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/start-here/preparing-your-data-for-import.md).

# Preparing your data for import

The two templates, what goes in each column, and how to get your data in without a failed import.

Your accounts and the people at them are the first things to get into Schedulink, because everything else attaches to them.

There are two templates, one for each. Fill them in, then either send them to us or import them yourself.

If you only have a handful of accounts, skip the import and [add them one at a time](#adding-records-one-at-a-time).

## Get the templates

[Download the accounts template](https://app.schedulink.io/import-sheets/accounts.xlsx)

[Download the contacts template](https://app.schedulink.io/import-sheets/contacts.xlsx)

Both are also available inside the app, from the Import option in the three-dot menu on the Accounts and Contacts pages.

Each template has an Instructions tab explaining every field with examples. Put your data straight into the templates, and leave the header row exactly as it is, because that's what the importer matches against.

Fill in Accounts first. Contacts attach to accounts by name, so the accounts have to exist before the contacts land.

{% hint style="info" %}
If you plan to use the **Template Name** column, build those account and contact templates before you import. The file is matched against templates that already exist.
{% endhint %}

## The Accounts template

### The account itself

| Column          | What goes in it                                                                                                                                                   |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Account Name    | The full name of the organisation. This is what appears on your calendar, and it's what your contacts file has to match                                           |
| Account Code    | A short unique reference, optional. Two accounts can't share one                                                                                                  |
| Phone           | The main office number                                                                                                                                            |
| Account Manager | The person at *your* studio who looks after this account, not someone at the organisation                                                                         |
| School District | The district or board, if it applies                                                                                                                              |
| Status          | Your relationship with them: Active, Prospect, Inactive, or whatever you use                                                                                      |
| Type            | The kind of organisation: School, Sports, Grad, Dance, Corporate, or your own categories                                                                          |
| Template Name   | The account template this account uses, which sets its custom fields. Copy the name exactly from Templates > Account Templates. Leave blank if you don't need one |

### Addresses

**Physical address**: Address 1, Address 2, City, State, Country and Postal Code, each suffixed with `- Physical`.

**Mailing address**: the same six columns suffixed with `- Mailing`.

If you need a third address, add another block following the same pattern: `Address 1 - Shipping`, `City - Shipping`, and so on.

## The Contacts template

| Column         | What goes in it                                                                                                                     |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| First Name     |                                                                                                                                     |
| Last Name      |                                                                                                                                     |
| Salutation     | Optional. Used in their display name and in automated emails: Mr, Mrs, Dr                                                           |
| Account Name   | Must match the account's name exactly, character for character. This is what links the person to the right account                  |
| Title          | Their real job title: Principal, Head Coach, Secretary. For your team's reference only                                              |
| Email          | Their email address. A general office address is fine if that's all you have                                                        |
| Phone #        | Their office line                                                                                                                   |
| Extension      | Their extension, if they have one                                                                                                   |
| Mobile         | Their mobile                                                                                                                        |
| Role1 to Role5 | What they do for you. One role per column, up to five                                                                               |
| Template Name  | The contact template this contact uses. Copy the name exactly from Templates > Contact Templates. Leave blank if you don't need one |

Roles go in separate columns, one each, rather than comma-separated into a single cell.

If someone works across several accounts, list them against the one you deal with them at most and add the others afterwards.

## Three columns that behave differently

Status, Type and Template Name all look like ordinary text, and they don't behave the same way.

{% hint style="warning" %}
**Status and Type create values.** They aren't checked against a list, they build one. Import a status of "Actve" and you now have a status called Actve in your dropdowns, sitting alongside Active forever. Nothing warns you.

So run your eye down those two columns before you upload. One studio's export had 142 different job titles that turned out to be about a dozen real ones with spelling variations, and that's the mess this creates.

**Template Name is the opposite.** It's matched against templates that already exist, and a name that doesn't match fails the whole import. Build the template first, then copy its name exactly.
{% endhint %}

## Title and role are different things

This catches nearly everyone, and getting it wrong is why emails don't arrive.

**Title** is their real job title at their organisation. It's there so your team knows who they're talking to, and it has no effect on anything the system does.

**Role** is what that person does *for you*. Its only job is to tell an email who to go to.

When you attach an email template to an event template, you choose which roles it should go to. At send time Schedulink looks at the account, finds everyone with those roles, and emails them.

So pick roles that match the emails you send:

| Role       | The email it receives                    |
| ---------- | ---------------------------------------- |
| Scheduling | Shoot date confirmations, date changes   |
| Data       | Roster and team list requests, reminders |
| Billing    | Invoices and payment reminders           |
| Yearbook   | Image delivery, yearbook deadlines       |

These are examples, not a fixed list. You create your own roles in **Setup > Preferences**, named however you like.

One person might hold Scheduling, Data and Billing at once, which is normal at a small school or a club run by volunteers. That's what the five role columns are for.

Two things follow.

**Several people can share a role.** If six coaches all have Scheduling, all six get the shoot confirmation, which is usually what you want for a league.

**If nobody at an account holds the role an email is looking for, the email doesn't send.** No error, it simply has nobody to go to. That's the first thing to check when someone says they never heard from you.

Fill roles in now if you can. Doing it in the template takes minutes; doing it later means opening every contact record one at a time.

## Sending it to us

If we're handling your onboarding, upload both files in the onboarding form. It accepts .csv or .xlsx up to 10 MB each, so you can send the templates as they are.

We import them and email you when your data is live, usually within two to three business days.

## Importing it yourself

When your accounts file is ready, save it as **.csv**. The importer wants CSV, and saving as CSV drops the Instructions tab, which is what you want.

1. Open **Accounts**
2. Click the three dots at the top of the page, next to the back button
3. Choose **Import**
4. Attach your file and click Upload

Then do the same in **Contacts**.

The importer is strict, and a single bad row rejects the whole file. It tells you what's wrong, so fix that in your sheet, save as CSV again and re-upload. Partial imports don't happen: nothing lands until everything passes.

The most common reasons are a duplicate account code, a missing or renamed column, a Template Name that doesn't match an existing template, and a contact whose Account Name doesn't exactly match an account.

## Adding records one at a time

For a few accounts, or for anything new mid-season, skip the import.

**An account**: open Accounts and click Add, top right.

**A contact**: open the account, scroll to Contacts, and add them there, so they're tied to the right account automatically.

## Stuck getting data out of your old system?

A normal place to get stuck, and we've pulled data out of most of the tools studios come from. Get in touch and we'll help you export it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/start-here/preparing-your-data-for-import.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
