Migrate from 24SevenOffice to Microsoft Project

24SevenOffice Projects map 1:1 to Microsoft Project. We preserve project name, description, status, start and finish dates, owner assignment, budget values, and milestone flags. PMI-standard alignment in the source platform means project metadata is well-structured for migration. 24SevenOffice project-level custom fields convert to Microsoft Project enterprise custom fields with type mapping applied during the transform phase.

Tasks and Subtasks under Projects migrate with parent-child hierarchy intact. We preserve assignees, due dates, status, estimated hours, and the original task hierarchy (WBS structure). Predecessor relationships are not natively structured in 24SevenOffice's REST API — if predecessors exist as custom fields or linked records in the source, we reconstruct finish-to-start links at migration time using task ID lookup. Custom task fields map individually with type conversion applied.

24SevenOffice Time Entries are standalone records linked to Projects and Users with billable/non-billable flags, timestamps, and duration. Microsoft Project stores effort on Task Assignments rather than as separate time entry records. We split each Time Entry by mapping it to the corresponding Task Assignment on the correct Project, setting the Assignment's remaining work and actual work fields to the logged duration, and preserving billable status as a custom Assignment field. Billing associations to Invoices require a secondary mapping note for the customer to handle in their accounting system.

24SevenOffice User accounts (name, email, role) map to Microsoft Project Resources. We resolve Users by email match against the destination resource list. If the source account uses role-based assignments (e.g., Developer, Project Manager) rather than individual resource assignments, we create typed Resources with those role names and set the Max Units accordingly. Resources without a matching destination identity go to the reconciliation queue for the customer's admin to provision before final import.

24SevenOffice custom properties (text, number, date, dropdown) on Projects and Tasks require explicit type conversion to Microsoft Project enterprise custom fields. Text maps to Text fields, numbers map to Number or Cost fields depending on whether the field represents monetary values, dates map to Date fields, and dropdowns map to Lookup Table fields with values created in the destination. We inspect the source schema during discovery, compare field types, and flag any incompatible conversions before the migration run begins.

24SevenOffice Notes attached to Projects or Tasks migrate as Project Documents. We extract note body content and re-attach it as a document record within the Project site in SharePoint (for Project Online) or as a document within the Project for the Web environment. Rich text formatting is preserved where the destination supports it.

File attachments referenced by URL in the 24SevenOffice API are downloaded to temporary storage, then uploaded to the associated SharePoint document library under the migrated Project. This applies to Project Online and Project for the Web, which both use SharePoint as the underlying document store. We flag any attachments associated with projects that will be created in a browser-only Project Plan 1 environment, where attachments require manual re-upload since the Plan 1 browser client does not support direct file attachment.

24SevenOffice tags (flat key-value labels on Contacts, Companies, and Deals) have no Microsoft Project equivalent. Project does not include a tagging schema. We extract all tags during discovery and deliver them as a CSV inventory with their associated record references, so the customer's admin can recreate them as enterprise custom fields, SharePoint column values, or Power Apps data if the tagging context is project-related.

24SevenOffice Company records (company name, industry, size, address, associated contacts) have no native Microsoft Project equivalent. Project stores Resources (people and roles), not organizational company records. If the customer's 24SevenOffice implementation uses Company as a project stakeholder or billing entity, we map Company names to Resource names and store the original Company identifier in a custom Resource field. Otherwise, we extract Companies as a separate CSV inventory for migration to a dedicated CRM if one is adopted.

24SevenOffice Deals and pipeline stages have no direct Microsoft Project equivalent. Microsoft Project tracks project schedules and resource assignments, not sales pipeline stages. We extract all Deals as a separate CSV with stage names, values, and owner assignments, and flag the Deal records as requiring a separate CRM migration target if the customer adopts Microsoft Dynamics 365 Sales or another CRM alongside Project.

24SevenOffice Invoices, Accounts Receivable, and Accounts Payable records carry country-edition-specific accounting schemas (Norwegian, Swedish, or UK tax codes and chart-of-accounts structures). Microsoft Project does not include accounting functionality. These records require a separate migration to a dedicated accounting platform such as Dynamics 365 Business Central, QuickBooks, or Xero. We extract Invoices and AR records as a separate dataset with the correct country-specific schema mapping applied and deliver them as a migration-ready CSV for the customer's chosen accounting destination.

24SevenOffice Contacts (individual people with name, email, phone, address, and lifecycle stage) map partially to Microsoft Project Resources for those who are assigned to tasks. Contacts who are project stakeholders or project managers become Resources; Contacts who are sales or customer relationship records should be flagged for migration to a dedicated CRM. We extract the full Contact list during discovery and apply the Resource mapping to those with project assignment history, delivering the remainder as a separate CSV inventory.