Migration

Bring your roster and seasons across.

See which records can be imported, what needs a managed service, and what starts fresh. Agree your scope and timing before the move.

Discuss migration Explore import paths See managed-service packages

Carried, not lost

Years of relationships move carefully, with people.

Rosters, seasons, services and repertoire come in through importers that check every row before anything is saved. Documents, contract templates and representation details move with our team.

Self-serve today

Apply for the workspace that fits you.
Import your roster from a CSV file and check every row in the preview.
Paste a season outline or a run of services straight from a spreadsheet.
Run setup, readiness, reports and My Week as soon as your workspace opens.

With our team

OPAS exports get a dry-run report before anything is written.
Payroll columns are matched to your own template, and you approve the mapping.
Document and library moves are checked for rights and for who may see each file.
Larger rollouts are scoped and priced as a managed service.

Checked before you rely on it

Every import shows you what will change before anything is written.
Before sign-off, an OPAS import can be rolled back. Later changes can leave conflicts that need review; rollback may be partial.
Re-running the same OPAS export creates nothing twice.
Run a real week side by side before you retire anything.

What we ask for

Samples, and how each one comes across.

Roster

How it comes across: CSV import
What we check: Names, emails, sections, instruments, roles and chairs.

Production week

How it comes across: Paste from a spreadsheet
What we check: Services, dates, call times, venue and repertoire.

OPAS export

How it comes across: Dry run first
What we check: Conflicts, invalid rows and exactly what will change, before anything is written.

Payroll template

How it comes across: Export profile
What we check: Your column order, delimiter and service categories, matched to your template.

Library and repertoire

How it comes across: Import and our team
What we check: The works catalogue by import; scores, parts and rights records moved with our team.

Engagement records

How it comes across: Archive or start fresh
What we check: Supported historical OPAS engagements can be imported as archived records. Old contract and invoice notes do not become verified signed contracts or paid invoices. New requests, holds and quotes start in Kalinklo.

Importers

What you can import today.

These importers are in the product today, and each one checks every row before anything is saved. Anything not listed is not imported automatically: our team moves it with you as a priced managed service, or it starts fresh in Kalinklo.

Spreadsheets (Excel · Google Sheets · Numbers)

Self-serve

Organizations import their players and staff from a CSV file, and paste a season outline or a run of services straight from a spreadsheet. Every row is checked before anything is saved, and problems are reported line by line.

Comes across

Players and staff: email, name, instrument, section, role and chair
Season outline: dates, title, conductor, soloist, the artist you need and the fee budget
Services: date, call, start and end time, type, title, venue and repertoire
Works catalogue: title, composer, duration, instrumentation and publisher

Not imported

Message history
Past invoices; new ones are issued in Kalinklo

OPAS

Dry run first

Preview your OPAS exports as CSV, TSV or a JSON bundle. Check invalid rows, conflicts and proposed changes before confirming an import. Repeating unchanged records does not create duplicates.

Comes across

People, sections and chairs
Seasons, productions and services, with times in your own time zone
Who plays what: service and production assignments
Repertoire and your document list

Not imported

Evaluation forms and custom named forms: no importer yet
Payroll history

Artist rosters, from any CSV export

Self-serve

Agencies export their artist list from whatever they use today, match its columns to Kalinklo's fields in the import preview, and bring it in. Rows that look like duplicates are held for review; only rows marked ready are imported.

Comes across

Artist name, email, instrument or role
City and country
Representation type, territory, status and dates
Commission percentage and notes

Not imported

Bookings, holds, quotes and contracts from the old system
Message history

Documents, contract templates and larger moves

With our team

Some things have no importer, and we don't pretend otherwise. Our team moves them with you as priced managed services, listed below.

Comes across

Production packets, riders, member documents and venue files, with their access rules
Contract templates in your house style
Agency roster, territories, fee notes and representation rules
Multi-season plans for orchestras and institutions

Not imported

Open bookings and holds: they are created in Kalinklo as the work continues
Anything you would rather leave behind

The five-stage migration

A careful move, at your pace.

Agree the timetable for these five stages around your records, data quality and team availability. Review the results before changing how your team works.

Discuss migration

Go through your current system, your volume, what comes across and what starts fresh, and the data processing agreement.

Sample import

Run a dry-run import on a small sample and check that every column lands in the right place.

Full import

Import the agreed records, check the results and review any source changes before the next import.

Side-by-side check

Run Kalinklo next to your current system and compare the week, the roster and the reports before anyone relies on it.

Switch when ready

You decide when Kalinklo becomes the record you work from. Keep the old system as an archive for as long as you like.

Managed services

Human setup where a clean launch needs it.

See pricing context

Agency roster migration

$5,000 – $25,000

scope-dependent

Bring roster, territories, fee notes, representation rules and request routing into Kalinklo. Agree source records, import scope and checks before migration.

Request scoping

Orchestra multi-year season import

$10,000 – $50,000

multi-year scope

Import seasons, conductor and soloist pipelines, approvals, budgets, and replacement presets.

Request scoping

Institution onboarding

$15,000 – $100,000

enterprise contract

Setup across venues, seasons and departments, with procurement mapping and support agreed in scope. SSO requires organization approval and testing with your identity provider.

Request scoping

Production Desk workspace setup

$7,500 – $25,000

launch sprint

Configure roles, sections, readiness, permissions, and first-week operating rhythm.

Request scoping

Organization document migration

$5,000 – $30,000

vault migration

Move production, member, venue, and approval files with controlled access and ownership.

Request scoping

Organization roster import

$3,500 – $20,000

member import

Import staff, players, guests, sections, roles, and assignments for a real personnel picture.

Request scoping

Contract template setup

$2,500 – $10,000

library buildout

Versioned engagement templates tailored to your house style and terms.

Request scoping

Ready to scope a migration?

Tell us what you use today and roughly how big your roster is. A person reads it and comes back with a scope and a price.

Request scoping See managed-service packages How OPAS migration works