Move your monday.com boards into Fareeqy

A Fareeqy task has one assignee, so the importer uses the leading name in the People value as the assignee reference you match during preview. It does not hide the other participants: the names from the People column are written in a clear line inside the task notes, and the preview reports that the source carried multiple assignees. You can keep one person accountable while retaining the people who shared the monday.com Item for reference.

The reader separates People names whether monday.com wrote them with commas or semicolons, then gathers distinct names across Board Items so the preview asks you to match each person once. It never connects by email or name similarity automatically because the Excel file carries a display name, not a Fareeqy member identifier. You decide which account corresponds to that value, preventing a task belonging to one Sara from reaching somebody else with the same name.

Excel carries no stable Item identifier for a later import to rely on, so the migration ledger falls back to the task title and its occurrence order inside the list. Upload the same Board again without changing titles and it can recognize rows that already arrived. Rename an Item in monday.com after migration and a later export may look like a new task. The preview shows what will be skipped or added, so never treat another upload as synchronization of people or titles.

If Person is selected as the grouping, the column values also name task lists. The default instead preserves the Groups your team authored in the Board, leaving People responsible only for assignment and the explanatory note. A People column hidden from the main view at export time cannot appear in Excel for the importer to read, so expose it and quickly check the workbook before upload. The preview cannot map a value monday.com never exported.

A monday.com Timeline is a range with a beginning and an end, while a Fareeqy task has one due date. The importer therefore does not pretend it recreated an equivalent range field. When a Timeline value contains both ends, the original range is written into the task notes under a clear heading. The planned duration remains readable after migration even though it does not become a separate scheduling object in the project.

A monday.com file is read from its actual layout, not treated as an ordinary flat table. The Board name sits above the sheet, a Group name appears alone, and a header row repeats before the Items in each Group. The importer recognizes that sequence and preserves every Group, including the one that appears before the initial header row. It then reads Timeline from the Item row itself, preventing a range from being confused with a group or board title.

What arrives still depends on the columns visible in the main view when Excel is created. Expose Timeline, Date, Status, and People when needed. A recognized Status such as Done or Complete can mark the task complete, while a custom label the importer cannot identify stays open instead of being guessed from a color absent from the file. Updates and Subitems are not present in Excel at all, so review those separately from the Timeline value retained in notes.