Migrate from Sonderplan to Asana

Sonderplan Bookings map directly to Asana Tasks. The booking's resource assignment (person, room, or equipment) is preserved as a custom field on the task—Booking_Resource_Name and Booking_Resource_Type for display. The booking's project reference maps to the Asana Project (created first so the Lookup is satisfied). The booking status maps to a custom task field that mirrors the customer's booking status vocabulary. Start and end timestamps from the booking become the task Due Date and a custom Start Date field if the customer requires both.

Sonderplan Resources of type person map to Asana Users by email address. We extract every distinct person resource from Bookings and cross-reference against the user's chosen Asana destination workspace. Resources without an email (rare) are flagged for the admin to either create a placeholder Asana User or convert to a custom field on the tasks they are assigned to.

Sonderplan Resources of type room or equipment have no direct Asana equivalent because Asana is not a resource scheduling tool. We preserve room and equipment assignments as custom fields (Booking_Room__c, Booking_Equipment__c) on the migrated tasks. If the customer wants to visualize room or equipment usage, we recommend Asana as the task system with a dedicated resource scheduling add-on (Skedulo, Resource Management by Asana, or a custom integration) operating in parallel.

Each Sonderplan Schedule becomes an Asana Team. The schedule name maps to the Team name, and all Bookings from that Schedule are imported into Projects within that Team. Shared resources that belong to multiple Schedules are flagged during deduplication scoping and assigned to the primary Team, with cross-schedule references noted in a custom field Booking_Secondary_Schedules__c for visibility.

Sonderplan Projects map directly to Asana Projects. The project name, description, and client association migrate as project fields. If the customer used client associations in Sonderplan as a separate contact reference, we map that to the Asana project member list or a custom client field. Projects are created before any Booking-to-Task import so that the parent project reference is satisfied.

Sonderplan contacts for team members map to Asana Users (active team members) or Asana Guests (external clients or collaborators). We extract contact type from the Sonderplan contact record if available, or infer from whether the contact appears as a resource assignee versus a client on bookings. All contacts receive a custom field Contact_Type__c to distinguish internal team members from external clients post-migration.

Sonderplan Quotes have no native Asana equivalent because Asana does not include billing or quoting objects. We export the full Quote record including line items (service, quantity, rate, total), quote status, and client association, and deliver a written inventory specifying the recommended Asana task structure to reproduce the quote (a parent task with subtasks per line item, or a custom Quote object via Asana's custom fields and sections). The customer or their implementation partner rebuilds quoting using Asana Tasks or a connected tool like HubSpot, QuickBooks, or Stripe.

Sonderplan Invoices carry billable items, payment status, and client association with no direct Asana equivalent. We export the full Invoice record including line items, amounts, payment status, and any partial payment history, and deliver a written inventory recommending how to structure Invoice tracking in Asana (custom fields on tasks, or a connection to a billing platform). Partial payments and credits are noted as custom fields on the parent task or project for reconciliation purposes.

Sonderplan account-specific custom fields on Bookings migrate to Asana custom fields on the Task object. We discover custom field schemas by exporting a random sample of 50 Bookings across all schedules and comparing field sets to catch sparse or recently added fields. Field types are mapped: text to Asana text, number to Asana number, date to Asana date, dropdown to Asana enum (drop-down). Required fields in Sonderplan are noted for the admin to configure as required in Asana after migration.

Sonderplan's calendar feed exports (iCal-style) are derived artifacts from the underlying booking data. We extract the source booking data directly rather than the feed format to ensure full field fidelity. The task start and due dates in Asana reflect the original booking time window from the calendar feed.

Sonderplan's Flexible Billing model means active user counts and resource counts fluctuate mid-cycle. We capture the billing snapshot at migration start (active users, active resources, current cycle dates) and deliver it as a written record so the customer can reconcile their final Sonderplan invoice against the migration cutover date. This is a reference document, not a data migration target.

Sonderplan's clash detection prevents double-booking of shared equipment or virtualized edit suites. This rule-based alert system has no Asana equivalent. We export any historical clash records as custom task flags (Clash_Detected__c, Clash_With_Resource__c) so that the customer can identify which migrated tasks were involved in double-booking events and address them manually in Asana.