Migrate from Sonderplan to Jira

Sonderplan Bookings map to Jira Issues (Story, Task, or Bug depending on booking type). The booking's resource assignment becomes the Jira Assignee field; the project reference becomes the Jira Project. Booking status (Confirmed, Tentative, Cancelled) maps to Jira Status with a custom Status Category or a dedicated workflow. Booking start and end dates migrate to Due Date and a custom startdate__c field for timeline rendering. Custom fields on Booking migrate to Jira custom issue fields created during schema design. Orphaned bookings (referencing deleted resources) are flagged in a reconciliation report before import.

Sonderplan Resources of type Person map to Jira User accounts. We resolve by email match against the destination Jira site's user directory. Any Resource without an email or without a matching Jira User is held in a reconciliation queue; the customer's admin provisions the Jira account before the booking import phase. Jira's free tier caps at 10 users, which affects the provisioning scope for larger teams—this is surfaced during scoping and may require a Standard plan upgrade before migration.

Sonderplan Resources of type Room or Equipment do not have a native Jira equivalent. We map them to Jira Labels (e.g., label:edit-suite-a, label:camera-body-5d) applied to the booking's parent Issue, with a naming convention agreed during scoping. For high-value or frequently booked equipment, we create a separate Jira Project per Resource Type and use Project membership as the room/equipment roster, then link booking Issues to that Project via a Project picker custom field.

Each Sonderplan Schedule maps to a Jira Project. The Schedule's name becomes the Jira Project name and key (e.g., SCHEDULE-NYC becomes NYC). Shared Resources belonging to multiple Schedules receive Labels from each Schedule namespace so that cross-schedule queries are possible. Multi-site configurations with separate Schedules per facility become separate Jira Projects under the same Jira Site, enabling org-level reporting across all facilities.

Sonderplan Projects map to Jira Epics within the destination Project. The Epic's summary is the Sonderplan Project name; the Epic's description carries the project client and any custom field values. Bookings under that project become child Issues (Stories or Tasks) linked to the Epic via the Epic Link custom field. If the customer prefers flat structure, we create a Jira Project per Sonderplan Project instead of Epic-per-Project—this is decided during scoping.

Sonderplan Contact records for clients do not map to a native Jira object. We create a client__c custom field of type Single-select (with options sourced from Sonderplan Contact names) and populate it on each Issue. If the customer uses Jira Service Management alongside Jira Software, contacts map to Customers in Jira Service Management. Email and phone from Sonderplan Contacts migrate as custom text fields on the client__c context.

Sonderplan Quotes (billable line items with service, quantity, and rate) map to Jira Issues with a quote__c custom field capturing the total amount, and a PDF attachment holding the original Quote document. The line-item breakdown is preserved in the Issue description field as a formatted table. Full line-item schema mapping to Jira Software's Estimate feature (Premium tier) is documented for the customer's admin if they hold a Premium license.

Sonderplan Invoices map similarly to Quotes: Jira Issue with an invoice__c custom field capturing total amount and payment status, and the original Invoice PDF as a Jira Attachment. Partial payments and credits are recorded in a custom payment_status__c field. Invoicing-as-code does not migrate; the customer rebuilds billing workflows in Jira if needed.

Sonderplan custom fields on Bookings (account-specific, discovered dynamically during export) map to Jira custom issue fields of equivalent type. Text fields become Jira Text Field; date fields become Jira Date Picker; numeric fields become Jira Number Field; dropdown fields become Jira Select List. We export all fields from a random sample of 50 Bookings and compare field sets to catch sparse custom fields before the full export. Jira field names are sanitized to remove special characters per Jira naming rules.

Sonderplan calendar feed exports (iCal-style) are a derived output of the underlying Booking data, not a primary data source. We export the underlying Booking records directly rather than the feed format, preserving full fidelity. The calendar feed itself is documented as a reconstruction task for the customer's admin using Jira's native calendar integration or an Atlassian Marketplace calendar app post-migration.