Migrate from Allfred to monday Work Management

Allfred Projects map to monday.com Boards as the top-level container. We extract project name, description, status (active/archived), start date, due date, and team assignments from Allfred's export. The Board is created in monday.com before any nested Items are imported, satisfying the parent dependency. Projects with a designated Kanban board in Allfred inherit that board's column structure as Groups or column types in monday.com.

Allfred Tasks map to monday.com Items. We preserve task title, description, assignee (mapped to monday.com Board member), due date, priority (mapped to Priority column), and status. Allfred task status values map to monday.com Status column values (To Do, Working on it, Stuck, Complete). Items are inserted after the parent Board is confirmed to exist.

Allfred Subtasks are nested under Tasks. Monday.com supports Subitems as a native feature on Items (available from Standard tier). We preserve the subtask title, assignee, due date, and status. The parent Task must be imported as a monday.com Item before the Subitem import runs. If the customer is on monday.com Basic (no Subitems), we flatten the hierarchy into Items with a parent reference custom field.

Allfred's Kanban Board structure — column names, column order, and task-to-column assignments — is extracted from the data export. Each Allfred Kanban Board becomes one monday.com Board with Groups representing columns (if the customer prefers a Kanban layout) or column types assigned to the existing board structure. Column naming conventions vary by project in Allfred, so we flag inconsistencies during discovery and normalize to a target schema the customer approves before import. WIP limit columns in Allfred require a custom solution in monday.com as WIP limits are not native.

Allfred Clients map to monday.com's native Clients product (available on CRM and higher tiers) or to a dedicated Client Board with a Client Name column. We extract company name, primary contact name, contact email, phone, and address from Allfred. If the customer uses monday.com Work Management without the CRM product, we recommend a Client Board as the equivalent. Client-to-Brand relationships are preserved through a Brand column or linked Board depending on the destination structure.

Allfred Brands are sub-entities under Clients containing brand name, logo, color palette, and brand guidelines. We map Brands to monday.com Tags (Workspace-level), Board-level Labels, or a dedicated Brand Board depending on how the customer uses Brand data. Logo and color palette values migrate as text references (URL or hex code) since monday.com does not natively host brand asset libraries. The customer chooses the strategy during scoping.

Allfred Contractors store name, contact details, hourly rate, and assignment history. Monday.com treats all workspace members as Users without a native Contractor object. We map Contractors to monday.com Users with a custom Contractor__c checkbox and hourly_rate__c number field, or alternatively to a separate Contractors Board if the customer needs ongoing contractor assignment tracking post-migration. The strategy is determined during discovery based on whether contractor-specific workflows are active.

Allfred Team Member records (name, email, role, avatar) map to monday.com Workspace members. We migrate all active team members with their assignment history on tasks and projects preserved as historical Item assignments. Archived or deactivated Allfred users migrate as inactive monday.com Users if their historical assignments need to remain linked; otherwise they are excluded from the active user roster.

Allfred per-project custom fields have no global schema, meaning the same logical field (e.g., Client Budget) may exist with different names or field types across projects. We extract all custom field definitions and their values per project, then map each to the closest monday.com column type (Text, Number, Date, Dropdown, Checkbox, Email, Phone, URL). We flag any fields that lose type fidelity during mapping (e.g., a multi-select in Allfred that maps to a single-select Dropdown in monday.com). The customer reviews and approves the per-project field map before we proceed.

Allfred provides unlimited file storage with a 2 GB per-file limit. We export all file attachments linked to Projects, Tasks, and Clients and upload them to the corresponding monday.com Board or Item. Files larger than monday.com's per-plan limit (5 GB on Standard, 100 GB on Pro, 1 TB on Enterprise) are chunked or flagged for the customer to host externally. File names and links migrate; inline preview thumbnails are regenerated by monday.com after upload.

Files stored via Allfred's SharePoint integration export as URL references rather than hosted blobs. We export these URLs as-is and insert them as external link columns in monday.com. If the destination monday.com workspace does not have SharePoint connectivity, these files may become inaccessible post-migration. We alert customers to any SharePoint-linked files during discovery and recommend migrating those files separately via SharePoint's native export tools before cutover.

Allfred allows data export of workspace configuration, notification preferences, and integration settings per its data ownership policy. We export these as a JSON bundle and deliver it alongside the migration for the customer's admin to reference when rebuilding workspace settings in monday.com. Settings are not applied programmatically since platform configuration schemas differ. Notification preferences and integration configurations require manual rebuild in monday.com's Workspace Settings.