Migrate from Allfred to Jira

Allfred Projects map to Jira Projects as the top-level container. Each Jira Project gets a default Issue Type Scheme defining which issue types (Epic, Story, Task, Bug) are available. Allfred project metadata (name, description, start/due dates, status) migrates to Jira Project fields. Jira Projects do not have a native description field at the project level in all configurations; project overview text migrates as a pinned Wiki Confluence page or stays in project-level custom fields.

Allfred Tasks map to Jira Story or Task issue types depending on customer preference during scoping. Subtasks nest under parent Tasks as Jira Sub-Tasks with the parent_id reference preserved. Allfred task fields (title, description, assignee, due date, priority, status) map to Jira Summary, Description (Markdown), Assignee (User), Due Date, Priority, and Status respectively. Jira status values are workflow-dependent and require a configured workflow before import.

Allfred Client records (company name, contact information) have no direct Jira equivalent. We map Clients to Jira Components within the destination Project, or to a separate Account-style custom field (Client Name, multi-select) on issues. The customer chooses the strategy during scoping based on whether they want client-level filtering across Jira Projects.

Allfred Brand sub-entities under Clients (brand name, logo, color palette, guidelines) require a custom field or Label in Jira since Jira has no native Brand object. Brand color and guidelines URL migrate as custom text fields. Brand-to-Client parentage is preserved by adding both Client and Brand to the issue record in Jira so the relationship remains queryable.

Allfred Contractors (name, contact, hourly rate, assignment history) do not have a native Jira equivalent. We migrate Contractor records to Jira User accounts, preserving name and email. Hourly rate and assignment history are not Jira-native fields and migrate to custom fields on the User record. The customer's Jira admin provisions the User accounts before migration or we create them with a flag for admin activation. Archived or inactive contractors migrate as inactive Jira Users.

Allfred Kanban board structure (column names, column order, task-to-column assignments) maps to Jira Kanban Boards. We extract the column configuration from the Allfred export bundle, create a corresponding Board in Jira, and map task assignments to the appropriate column via the Jira Backlog or Board column configuration. If Allfred boards use custom column naming conventions, we document them in the mapping notes for the customer's Jira admin to configure in the Board settings.

Allfred per-project custom fields require a global schema pre-creation in Jira before migration. We extract every unique custom field definition from the Allfred export, deduplicate across projects (same field name but different types = separate Jira fields), assign Jira field types (Text, Number, Date, Select, Multi-select), and submit the Jira field creation manifest for customer approval. Import fails without pre-created Jira custom fields because Jira requires the field ID at import time. This is the highest-risk step in the migration and requires explicit sign-off.

Allfred Team Members (name, email, role, avatar) map to Jira Users by email match. We extract every distinct team member from Projects, Tasks, and Kanban boards, match against the Jira destination instance's User table, and provision any missing Users in a reconciliation queue. Role in Allfred (Admin, Member, Contractor) maps to Jira project roles (Administrators, Members) which are configured per Project.

Allfred file attachments linked to Projects and Tasks migrate to Jira Issue Attachments via the Jira REST API. Files must be under Jira Cloud's attachment size limit (up to 10 MB depending on plan). Files stored via Allfred's SharePoint integration export as URL references only; these migrate as text URLs in a custom field rather than as hosted files, and the customer must ensure SharePoint access persists post-migration.

Allfred workspace settings, notification preferences, and SharePoint integration configurations export as JSON but do not have direct Jira equivalents. We deliver these as a JSON export in the migration handoff documentation for the customer's admin to evaluate for manual reconfiguration in Jira. No settings import into Jira occurs.