Milestones are a flag on a task that marks a major checkpoint in a project. To designate a task as a Milestone, you simply enable the Milestone option in the task’s details. This is the direct way to mark the item as a milestone and have it appear with milestone styling in views like timelines. Other actions don’t set the milestone status: there isn’t a separate project type called Milestone, you don’t convert a task into a separate milestone task, and a label at the top isn’t how you designate milestones. The Milestone toggle in the task’s details is what makes it a milestone.

The key idea is to handle migration with a planned, controlled process that preserves data integrity. Start by mapping your source data to Asana’s fields (tasks, projects, sections, assignees, due dates, custom fields). Then use a CSV import to bring in the data in bulk, ensuring each field lines up with the appropriate Asana field. Validate the import with a small sample first to catch any format or mapping issues before bringing in everything. Clean duplicates and correct any mismatches so you don’t carry over old duplicates or misassigned information. Finally, roll the migration out in stages, testing with a subset of users or projects to confirm everything works as expected before a full rollout. This approach is superior because it prevents data gaps and misaligned fields, avoids the chaos of unstructured imports, and minimizes disruption by validating and iterating before a wide release.

Custom fields in Asana are designed to hold different kinds of structured data attached to tasks. The data types you can store in a custom field are text for free-form words, number for numeric values, date for calendar dates, dropdown for selecting from predefined options, and checkbox for true/false. Each type uses its own UI control—text boxes, numeric input, date picker, dropdown menu, or a checkbox—so you can enter exactly the kind of data you need. Images and audio aren’t stored in a custom field; they’re attachments on the task. A field that only stores one type would miss the other kinds of data you might want to track, and a field focused on dates alone wouldn’t cover the full range of data you can capture with custom fields.

Regular, timely review of messages and updates keeps you aligned with what’s happening in the project. Checking your inbox twice a day helps you catch mentions, task changes, and comments early, so you can respond promptly and prevent a growing backlog. Checking only once a week or only when you’re assigned misses updates and slows progress, because new information can arrive at any time and requires your attention. Disabling notifications hides new messages, making it easy to miss critical context and cause delays. Keeping a routine of checking twice daily balances staying informed with maintaining focus.

In Timeline and Gantt views, dependencies are shown as visual links between task bars, indicating the sequence that must be followed. You can create a new dependency by drawing a connection from one task to another, which locks the second task to wait for the first to finish. This setup helps you plan work flow, see which tasks are blocked, and watch how changes to one task affect its dependents—the schedule automatically adjusts for linked tasks. The other options don’t reflect how dependencies work in this view: changing colors, editing descriptions, or importing dependencies from Excel aren’t how you manage task dependencies in Timeline.