Turn your spreadsheet into projects and tasks

Yes. The importer recognizes headers such as the Arabic words for task, task name, description, status, assignee, and due date, alongside their English equivalents. Only the task-name column is required; the others are optional. Matching does not depend on a fixed column order, so your familiar sheet layout can stay intact. If a header is unknown, we do not guess its meaning and attach it to a field you may not have intended.

Matching normalizes letter forms and whitespace, then ignores Arabic diacritics and elongation while comparing a header, allowing two written forms of the same word to behave alike. The reader knows practical aliases: Title or Item can name a task, Responsible or Assigned To can name its owner, and Due or Deadline can carry the date. Arabic and English headers can appear in the same file when a bilingual team naturally mixes them.

A Project column determines how workbook sheets relate to projects. When it exists, one sheet can contain rows for several projects and the values split them accordingly. Without it, each Sheet name becomes an independent project name. A CSV uses its file name for that level. The reader excludes the selected grouping column from project naming, preventing every phase value from becoming a project with only one list, then exposes the result in preview before creating any record.

Other columns can shape the import without forcing a template. Project or its Arabic equivalent separates rows into projects, while Section, Phase, or their recognized Arabic forms can create task lists. Status determines completion when it contains a known value. Tags and Priority text can remain in notes. Read the project, list, and person names in the preview before confirmation; that is where you verify that your own headers meant what the reader understood them to mean.

Excel sometimes stores a date as a serial number rather than visible text inside the xlsx file. The reader recognizes a number in a realistic date range and converts it into the task's due date. It also understands common date formats from CSV files saved under different regional settings. If one value is malformed or cannot be read safely, that task remains without a due date instead of causing the entire spreadsheet import to fail.

The reader also handles a common device-setting difference. Excel in a comma-decimal locale may save CSV with semicolons between columns, so delimiter detection prevents the whole row from landing in one cell. Arabic and Western encodings are tried after UTF-8 when the file does not identify itself clearly, protecting task names from turning into unreadable symbols. ISO dates, month-name formats, and day-before-month forms from common exports are recognized.

Not every number is treated as a date because an Estimate, cost, or order identifier may sit nearby. Conversion is applied to the due-date field and accepted only within a realistic calendar range. Separately, Status values such as done, complete, and their recognized Arabic equivalents can mark completion. The formula that produced an xlsx date does not transfer; only the value cached when the workbook was saved arrives. Save after the latest recalculation before uploading.