Skip to main content
Kalinklo · Artists

Migration

Bringing your roster across.

What carries forward, what resets, and how long it takes. We don't pretend migration is one-click. The honest answer: 7–14 days of joint work with our managed-services team, depending on volume.

See managed-service packages Book a scoping call
An empty concert hall before a performance

Carried, not lost

Years of relationships do not move in one click — they move carefully, with people.

Visual reference only — no venue or institution partnership is implied

Sources we've mapped

What we know how to import.

Each source below has a documented column map. For systems not on this list, our managed-service team can usually scope a custom import inside 7 days.

Spreadsheet (Excel · Google Sheets · Numbers)

Spreadsheet import

The most common starting point — a roster, a calendar, a season plan, an invoice register. We map columns to entity fields and load.

Carried forward

  • Artists, agencies, presenters with names + contact
  • Confirmed bookings with date + venue + program
  • Open holds with expiry
  • Contract templates as PDF in vault

Reset / out of scope

  • Historical messages (no source schema)
  • Internal notes without explicit consent
  • Past invoices unless re-issued through the platform

Overture

On request

Overture is internal-CRM-first; export their workflow data into CSV, share with managed services, and we map agency · roster · holds · quotes through the import pipeline.

Carried forward

  • Agency roster + representation agreements
  • Active holds with expiry dates
  • Open quotes (status preserved)
  • Standard contract templates

Reset / out of scope

  • Internal CRM notes (privacy default)
  • Closed/historical bookings unless explicitly requested

Gigwell

On request

Gigwell exports to CSV through their reports module. We map tour data → Booking, contracts → Contract, advancing checklists into the new Document Vault.

Carried forward

  • Tour bookings with venue + date + status
  • Contracts (as PDF in vault)
  • Advancing documents (as tagged Document Vault entries)
  • Buyer + agency contacts

Reset / out of scope

  • Routing/itinerary calendar (planned feature)
  • Backline + production rider templates require remapping

Prism.fm

On request

Prism's CSV export carries booking + offer data. We map offers → Quote, confirmed shows → Booking, settlement → Invoice with line items.

Carried forward

  • Offers (status: SENT / ACCEPTED / DECLINED)
  • Confirmed bookings + venues
  • Settlement summaries (re-issued as Invoices)

Reset / out of scope

  • Prism's promoter-side data (not in scope for an agency workspace)

ABOSS

On request

ABOSS export to CSV + XML covers EU compliance schema. We import roster, holds, quotes, and contracts; XML invoices preserved in the vault.

Carried forward

  • Roster + representation
  • Active holds + quotes
  • Contracts + e-invoicing XML in vault

Reset / out of scope

  • Travel/advancing module (planned)

The five-stage migration

7–14 days, end-to-end.

Most migrations land in this window. Heavier ones (multi-season orchestra import, full institutional rollout) follow the same five stages over a longer interval.

  1. 1

    Day 1

    Scoping call

    Walk through the source system, the volume, and the deal types. Decide what's carried vs reset. Sign the Data Processing Agreement.

  2. 2

    Day 1-3

    Sample import (5 rows per entity)

    We take five artists, five bookings, five contracts and load them into a sandbox workspace you can poke. Confirms the schema mapping is right before bulk run.

  3. 3

    Day 3-7

    Full migration + delta sweep

    Bulk import. Run a delta sweep to catch entities created during the migration window. Snapshot the source system one last time for audit.

  4. 4

    Day 7-14

    Parallel-run validation

    Your team runs day-to-day work in Kalinklo with the source system still readable but read-only. We compare every new entity created during this window to confirm parity.

  5. 5

    Day 14+

    Cutover + sunset

    Source system is fully retired (or kept as a read-only archive). You're on Kalinklo for new engagements. Managed services contract closes on milestone.

Four commitments

What we sign on for.

No-fault rollback

If anything in the parallel-run window doesn't match, we suspend the migration and restore the source system to operating order. No questions.

Your data, your control

You retain full ownership of every row imported. Export the workspace back to CSV at any point, in any plan.

No retroactive fees

Managed migration is billed once at the agreed scope. Booking fees only apply to engagements created after cutover — never to historical bookings.

Audit chain preserved

Every imported entity carries a provenance metadata key noting source system + import date + sample-check status. Visible to admin in /admin/audit.

Scope a migration

Ready to scope a migration?

Send your current system + rough roster size. We'll quote scope within three business days.

Request scoping See packages Compare
Request accessSign in