The system is already wired. Your job is to replace the sample records, not rebuild the architecture.
<aside>
⚡
Fastest path: keep the sample records for five minutes, add one real project, one milestone and three real tasks, then remove the samples once the flow makes sense.
</aside>
1. Choose your starting mode
Explore with sample data
Best if you want to understand the system first.
- Open Workflow 101 and move through the task views.
- Open one sample project and see how milestones and tasks stay linked.
- Scan OPS Dashboard to see priorities, deadlines, blockers and project health.
Start clean
Best if you already know the model.
- Add your real Projects first.
- Add Milestones and connect each one to a Project.
- Add Tasks and connect each one to a Project and, when useful, a Milestone.
- Remove sample records only after your real records are visible in the dashboards.
2. Replace the sample data
Every sample record is marked with the Demo checkbox. In Admin, filter Demo = checked when you are ready to clean the template.
Remove sample records in this order so you do not leave orphaned work behind:
- Tasks
- Milestones
- Meetings / Decisions / Notes / SOPs
- Projects
You can also rename and reuse the sample projects instead of deleting them. New records start with Demo unchecked.
3. Set ownership
- Owner is plain text on purpose. It survives duplication cleanly and works well for role-level accountability such as Operations Lead or Client Lead.
- Assignee on Tasks is a Notion Person property. Assign real team members there and the Assigned to Me view in Workflow 101 becomes personal automatically.
- If one person owns both accountability and execution, use the same person/role in both fields. If not, keep the distinction.
4. Bulk migration
For existing work in Notion, ClickUp, Asana or spreadsheets:
- Export the relevant entities to CSV.
- Import Projects, Milestones and Tasks into their matching source databases under Admin.