Migrate from Allfred to Microsoft Project

Allfred Projects map directly to Microsoft Project project files or Project Online project records. We extract project name, description, status, start date, finish date, and assigned team members. Allfred's project-level custom fields migrate to Microsoft Project custom fields (Text1-30, Number1-20, Flag1-20) that we configure during the destination schema setup phase. Microsoft Project's project summary task is used as the equivalent of Allfred's project-level overview.

Allfred Tasks map to Microsoft Project Tasks with Name, Start, Finish, Duration, Priority, and Notes preserved. Subtasks in Allfred become child Summary Tasks in Microsoft Project with their own subtasks nested beneath. Task hierarchy is preserved through the parent_id references in the Allfred export. We flag any Allfred tasks that reference milestone-like behavior (zero duration markers) and map them to Microsoft Project milestone tasks.

Allfred's distinct Client object has no direct Microsoft Project equivalent. We map Clients to a custom text field (ClientName__c) on project tasks, or we create a Client-level summary task at the top of the project plan as a grouping row. The customer chooses the strategy during scoping. Client contact information (name, email, phone) migrates to the project summary task notes or a custom ContactInfo__c field.

Allfred Brands sit under Clients and store brand name, logo, and brand guidelines. Since Microsoft Project does not have a Brand entity, we map Brands to a custom text field (Brand__c) on the relevant tasks. If the customer manages multiple brands per project, we configure Brand as a multi-select custom field or as separate task groupings under the project plan. The Allfred Brand-to-Client relationship is preserved by linking tasks to the Client-level summary row.

Allfred Contractors store name, contact details, and hourly rate. Microsoft Project Resources store name, type (Material or Work), standard rate, overtime rate, and calendar. We map each Contractor to a Resource with the Allfred hourly rate set as the Standard Rate. If Contractors have varying rates per project, we create a Resource custom field (ContractorRate__c) and document the per-project rate assignments for manual entry post-migration. Allfred's Contractor assignment history on tasks maps to Resource Assignments in Microsoft Project with Units and Work values calculated from task duration.

Allfred Kanban boards expose column names, column order, and task-to-column assignments via the data export. Microsoft Project has no native Kanban representation. We transform the Kanban structure into task groupings (using outline levels or summary tasks per column) or into a custom Text field (KanbanColumn__c) that preserves the original column assignment on each task. The customer selects the preferred representation during scoping. WIP limits from Kanban columns cannot be enforced in Microsoft Project and are documented as a PMO process note.

Allfred Team Members (internal staff) map to Microsoft Project Work-type Resources with the team member's name, email, and role preserved. We resolve Team Members by email against the Allfred export and create Resource records with Default Booking Type set to Committed. If a Team Member is also listed as a Contractor in Allfred, we create a single Resource record and flag it for the customer to set the appropriate cost rate.

Allfred allows per-project custom fields without a global schema, meaning the same logical field may exist with different names or types across projects. We extract all custom field definitions during discovery, deduplicate them by logical name and type, and map them to Microsoft Project's fixed custom field slots (Text1-30, Number1-20, Date1-10, Flag1-20, OutlineCode1-10). Customers review and approve the per-project field map before we proceed, as mismatched field types cause data loss or validation errors in Microsoft Project.

Allfred's unlimited file storage with 2GB per-file limit means large creative assets may exist. We export file attachment URLs as-is. For files stored via Allfred's SharePoint integration, we preserve the SharePoint URL references. Microsoft Project (desktop) does not host files natively; Project Online uses SharePoint document libraries. We migrate SharePoint URLs as hyperlinks in task notes or as a document library link on the project summary task. Files exceeding typical SharePoint upload limits (250MB) are flagged for manual re-upload via SharePoint's native tools.

Allfred exports workspace configuration, notification preferences, and integrations as JSON. We extract these for documentation purposes but do not import them into Microsoft Project, which has a different settings model. We deliver a written settings inventory covering Allfred notification rules, integration endpoints, and workspace preferences that the customer's admin uses to configure equivalent settings in Microsoft Project and the surrounding Microsoft 365 environment.