Skip to main content
KalinkloOS

Migration

Bringing your roster across.

What carries forward, what resets, and how long it takes. Migration is not one click: most projects take 7–14 days of joint work, depending on volume.

An empty concert hall before a performance

Carried, not lost

Years of relationships move carefully, with people.

Most migrations fit this window. Multi-season or institutional rollouts use the same stages over a longer interval.

Self-serve today

  • Create or request the right workspace.
  • Import a supported roster CSV.
  • Use access codes when email is not proven.
  • Run setup, readiness, reports, and My Week after an approved release.

Reviewed by hand

  • Legacy exports receive a dry-run report before import.
  • Payroll columns require mapping and customer signoff.
  • Document migrations require rights and access review.
  • Large organizations require provider proof before broad invitations.

Proven before reliance

  • Email delivery is verified before members depend on it.
  • Payments activate only after end-to-end provider verification.
  • E-signature activates after the signing provider is confirmed.
  • Real import, payroll, and first-week workflows are proven before launch is complete.

Customer sample inventory

What we ask for, and how it is handled.

SamplePathProof expected
RosterCSV importNames, contacts, sections, instruments, roles, and substitutes.
Production weekReviewed sampleProduction, services, call times, venue, assignments, and seating.
OPAS exportDry run firstExternal IDs, conflicts, invalid rows, idempotency, and rollback proof.
Payroll templateMapped profileColumns, delimiter, service categories, lock, and signoff evidence.
Library and repertoireScoped migrationMetadata, rights, inventory, works, and performance history.
Engagement recordsStructured reviewRequests, holds, quotes, contracts, invoices, settlement, and archive.

Sources we've mapped

What we know how to import.

Each source has a documented column map. Other systems can usually be scoped for custom import within seven days.

Spreadsheet (Excel · Google Sheets · Numbers)

Spreadsheet import

We map roster, calendar, season, document, and invoice-register columns to platform entities.

Carried forward

  • Artists, agencies, presenters, and contacts
  • Confirmed bookings with date, venue, and programme
  • Open holds with expiry
  • Contract templates and weekly files in the vault

Reset / out of scope

  • Historical messages without a source schema
  • Internal notes without explicit consent
  • Past invoices unless re-issued

Overture

Bring as CSV

Export workflow data to CSV and we map agency, roster, holds, and quotes through the import pipeline.

Carried forward

  • Agency roster and representation
  • Active holds with expiry
  • Open quotes with status
  • Standard contract templates

Reset / out of scope

  • Internal CRM notes by default
  • Closed history unless requested

Gigwell

On request

We map report CSV tour data to bookings, contracts to the vault, and advancing documents to tagged entries.

Carried forward

  • Tour bookings with venue, date, and status
  • Contracts as vault PDFs
  • Tagged advancing documents
  • Buyer and agency contacts

Reset / out of scope

  • Routing and itinerary calendar
  • Backline and rider templates without remapping

Prism.fm

On request

We map offers to quotes, confirmed shows to bookings, and settlement to invoices with line items.

Carried forward

  • Offers with sent, accepted, or declined status
  • Confirmed bookings and venues
  • Settlement summaries re-issued as invoices

Reset / out of scope

  • Promoter-side data outside Agency OS scope

ABOSS

On request

CSV and XML exports cover roster, holds, quotes, contracts, and preserved e-invoice XML.

Carried forward

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

Reset / out of scope

  • Travel and advancing module

The five-stage migration

7–14 days, end-to-end

Day 1

Scoping call

Review source, volume, deal types, carried versus reset data, and the DPA.

Day 1–3

Sample import

Load five rows per entity in a sandbox and confirm schema mapping.

Day 3–7

Full migration + delta sweep

Bulk import, catch records created during migration, and snapshot the source for audit.

Day 7–14

Parallel-run validation

Run Kalinklo while the source remains read-only and compare every new entity.

Day 14+

Cutover + sunset

Retire the source or keep a read-only archive and close on the agreed milestone.

Managed services

Human setup where a clean launch needs it.

See pricing context

Agency roster migration

$5,000 – $25,000

scope-dependent

Migrate roster, territories, fee notes, rules, routing, portal, and optional history.

Orchestra multi-year season import

$10,000 – $50,000

multi-year scope

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

Institution onboarding

$15,000 – $100,000

enterprise contract

Multi-venue, season, and department setup with SSO roadmap, procurement mapping, and dedicated support.

Production Desk workspace setup

$7,500 – $25,000

launch sprint

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

Organization document migration

$5,000 – $30,000

vault migration

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

Organization roster import

$3,500 – $20,000

member import

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

Contract template setup

$2,500 – $10,000

library buildout

Versioned engagement templates tailored to your house style and terms.

Ready to scope a migration?

Send your source system and rough roster size. We quote scope within three business days.

Migration | Kalinklo