Migrate from Sonderplan to Microsoft Project

Sonderplan Bookings map to Microsoft Project Tasks. The Booking start date maps to Task Start, end date to Task Finish, and the booking status (confirmed, tentative, cancelled) maps to a custom Task Status field or Task Percent Complete derived from status. Resource assignments on the Booking (person, room, or equipment) map to Task Assignments on the corresponding Resource Sheet entry with the Booking duration converted to hours for the Units field. Custom fields on the Booking (client, project phase, shoot day, location) map to Task-level custom fields created in Project Web App or as custom columns in Project Desktop.

Sonderplan Resources of type Person map to Microsoft Project Resource Sheet entries as Work resources with a per-hour cost rate. The resource name and email map to Name and Initials. We preserve the Schedule membership as a custom Resource field resource_schedule__c in case multi-schedule membership needs to be reconstructed in the destination. Hourly rates from Sonderplan map to the Cost Rate table on the resource.

Sonderplan Resources of type Room or Equipment map to Microsoft Project Material resources with a per-use cost rate, or Work resources with an hourly cost depending on how the customer prices these in Sonderplan. We use the resource type indicator from Sonderplan to set the Resource Type in Project. Equipment with peak utilization tracking in Sonderplan maps to a custom Material resource with Max Units set to 1 to enforce singular allocation.

Each Sonderplan Schedule maps to a separate Microsoft Project file (MPP) or, in a Project Web App environment, to an Enterprise Project. Shared Resources (edit suites, shared equipment) that belong to multiple Schedules are entered once in the Enterprise Resource Pool and referenced by each Project. The multi-schedule-to-multi-project split is applied at migration time; we create all Projects first, then resolve Resource Sheet cross-references.

Sonderplan Projects map to Microsoft Project Summary Task rows within the destination project, or as a Project-level custom field value if the destination is Project Online. The Project client association maps to a custom Project field (Project Client) that we create in Project Web App. Phase and milestone structure from Sonderplan translates to summary Tasks and milestone Tasks (duration = 0, milestone = Yes) in Microsoft Project.

Microsoft Project has no native client or contact object. Client contacts from Sonderplan are migrated as values in a custom Task-level text field (Project Client) and as a custom Project field (Client Name). If the destination is a Project Online SharePoint task list, contacts can be stored in the associated SharePoint site list. We document the chosen strategy during scoping and apply it consistently across all records.

Team members who are resources map to Resource Sheet entries (see Resource mapping above). Team members who are project stakeholders but not resource-assigned map to a custom Project field (Project Team) with names listed as a text string. For organizations with a SharePoint Online environment attached to Project Online, we recommend a SharePoint contact list as the long-term home for stakeholder contacts.

Sonderplan custom fields are discovered by exporting a random sample of 50 Bookings and comparing field sets to catch sparse or recently added fields. Discovered custom fields are created in the destination as Task-level Enterprise Custom Fields in Project Web App (with typed field definitions: Text, Flag, Date, Number, or Cost) or as custom columns in Project Desktop. We do not assume field type from the data sample alone; we inspect the Sonderplan field definition for type if available.

Sonderplan project-level custom fields (episodic production folders, shoot locations, delivery formats) map to Project-level Enterprise Custom Fields in Project Web App. These are created as Project fields with a Lookup Table if the values are finite (e.g., delivery format options) or as a text field if open-ended. Project Custom Fields are set at the project summary level and inherited by all tasks within the project.

Sonderplan Quotes have line-item structures (services, quantities, rates) that do not map to any native Microsoft Project object. We export Quote records as a structured CSV and attach the CSV as a document link on the destination Project Summary Task or Project-level custom field (Quote Reference). The customer's admin reconciles billing outside of Microsoft Project or via a third-party PSA integration.

Sonderplan Invoices carry payment status and billable amounts that do not map to native Microsoft Project objects. We export Invoice records as a structured CSV, tag each Invoice to the associated Project via a custom Project field (Invoice Reference), and attach the invoice CSV to the Project. Partial payments and credits are preserved as line-item notes in the CSV. Financial tracking beyond this is outside the scope of Microsoft Project and requires a PSA or ERP integration.

The Sonderplan calendar feed export is a derived artifact of Booking data. We extract the underlying Booking records directly rather than parsing the iCal-style feed, ensuring full field fidelity including custom fields, resource assignments, and booking status. The calendar feed itself is not migrated as a feed; the booking data within it is migrated as Tasks.