How to Unify Tasks in Notion from Basecamp, Gmail, and Slack
Unify tasks in Notion from Basecamp, Gmail, and Slack with one Tasks database, linked views, and automated intake. See the schema, views, and Zaps to use.
Notion ops system to replace Asana + spreadsheets
Build a Notion operations system to replace Asana and spreadsheets: six connected databases, field report forms, rollups, and campaign views your team will use.
TABLE OF CONTENTS
You can replace scattered Asana projects and spreadsheet trackers with a single Notion operations system. Model your work as connected databases (campaigns, venues, visits, trips, payments, and field agents), then use filtered views and forms so every update rolls up to the right campaign. The example below is built for a field marketing team running in-store campaigns, but the same pattern fits any ops team juggling locations, people, and payouts.
What a Notion operations system needs to replace
If your current setup looks like “tasks in Asana + data in spreadsheets,” the gap usually isn’t task tracking. It’s visibility:
- You need to click into one campaign and see everything that belongs to it.
- You need updates from the field to land in the right place automatically.
- You need a way to track money (owed/paid/reimbursed) without breaking reporting.
Notion handles this well, but it starts as a blank slate. You get a fully connected system; you pay for it in build time.
The core schema: 6 databases that stay readable
This is the simplest structure that still supports real ops reporting.
1) Campaigns (the parent record)
Each row = one campaign.
Suggested properties:
- Status (Planning / Live / Auditing / Complete)
- Client (text or relation, depending on your setup)
- Start date / End date
- Regions / Markets (multi-select)
- Budget (number)
- Primary owner (person)
Key relations:
- Venues (relation)
- Venue Visits (relation)
- Trips (relation)
- Payments (relation)
- Field Agents (relation)
2) Venues / Storefronts
Each row = one storefront/venue.
Suggested properties:
- Address (Place property, which also gives you a map view of every venue)
- Market / City
- Venue status (Active / On hold / Removed)
- Rate (number)
Key relations:
- Campaigns (relation)
- Venue Visits (relation)
- Payments (relation)
3) Venue Visits (field reports)
Each row = one visit (install, audit, removal, re-check).
Suggested properties:
- Visit type (Install / Audit / Removal)
- Visit date
- Photo / files
- Notes
- Outcome (Passed / Needs fix)
Key relations:
- Campaign (relation)
- Venue (relation)
- Trip (relation)
- Field Agent (relation)
4) Trips (routes and schedules)
Each row = one trip plan.
Suggested properties:
- Trip window (date range)
- Route summary (text)
- Estimated cost (number)
- Approved? (checkbox)
Key relations:
- Campaign (relation)
- Field Agent (relation)
- Venue Visits (relation)
5) Payments (what’s owed and what happened)
Each row = one payment event.
Suggested properties:
- Payment type (Venue payout / Agent reimbursement)
- Amount (number)
- Due date
- Paid? (checkbox)
- Payment method (select)
Key relations:
- Campaign (relation)
- Venue (optional relation)
- Field Agent (optional relation)
- Trip (optional relation)
6) Field Agents
Each row = one contractor/agent.
Suggested properties:
- Markets covered
- Rate / terms
- Status (Active / Paused)
Key relations:
- Trips (relation)
- Venue Visits (relation)
- Payments (relation)
The views that make this feel “fast”
The model above only works if people can see what they need quickly.
Campaign dashboard (single source of truth)
Inside each campaign page:
- A “Venues for this campaign” view filtered to that campaign
- A “Visits” view grouped by Visit type and/or Outcome
- A “Trips” view grouped by status/approval
- A “Payments” view filtered to unpaid and due soon
Ops inbox view (work triage)
A cross-campaign view for the ops owner:
- Visits needing follow-up
- Trips not approved
- Payments overdue
Finance view
- Payments grouped by Paid? and Payment type
- A “due this week” filter
Add a form so the field work comes back clean
The biggest time-saver is turning field reports into a form submission.
Add a form view to the Venue Visits database with questions like the ones below. Notion forms support relation questions, so agents pick the campaign and venue from a list instead of typing them (as of October 2026):
- Campaign
- Venue
- Visit type
- Photos
- Notes
- Outcome
When a field agent submits the form, the visit is created and immediately appears under the campaign via relations and rollups.
Rollups to keep campaigns readable
Once relations are in place, rollups let the Campaign record summarize reality:
- Number of venues
- Number of installs completed
- Number of audits completed
- Amount owed (unpaid)
- Next scheduled trip date
Keep rollups minimal. Too many of them make campaign pages noisy.
Implementation plan (a practical way to build without stalling ops)
A reliable way to build this without disappearing for weeks:
- Build only Campaigns + Venues + Venue Visits.
- Add the Venue Visit form and start capturing field work.
- Add Trips once you know what “trip plan” means in your process.
- Add Payments last, once you’ve defined what counts as a payment event.
Where Asana still wins (and how to handle it)
Asana is excellent for fast task assignment and due dates. If you’re not ready to fully switch, use Notion as the system of record and keep Asana only for task reminders.
If you want to migrate fully, create a lightweight Tasks database in Notion only after the ops data model is working.
Skip the trial-and-error
Designing six connected databases, the views, and the field form usually takes an ops team a week or two of evenings to get right. If you’d rather skip the trial-and-error, book a ZoomFlow session. One of our consultants will build your Notion operations system with you on a live call, and you’ll own it when we’re done.
Related Posts
Harvest project setup for Hive clients (time tracking)
Set up one Harvest project per Hive client, assign consultants, and set billable rates so time tracking works and every engagement shows up on timesheets.
QuickBooks invoicing + project tracking: a lightweight setup
Set up QuickBooks invoicing with a lightweight project workflow: draft invoices, approval steps, and status sync—without buying a heavy PM suite.
