Skip to content
Current/ Help Center

Create a project: from scratch, a playbook, or a won quote

3 min read · Updated Sep 4, 2026

There are three starting points for a new project in Current: build it from scratch, clone it from a playbook, or convert it straight from a won quote. All three end up in the same place — a project with phases, tasks, and (optionally) a link to your PSA — so pick whichever gives you the most of the work already done.

Start from scratch

Click New project from the Projects list. The dialog asks for the basics — you can refine phases, tasks, and dependencies afterward.

  1. 1
    Name the project
    A short, specific name works best, e.g. "M365 tenant migration."
  2. 2
    Pick a partner (optional)
    Start typing a partner's name. If it doesn't already exist in Current, typing a new name creates it.
  3. 3
    Choose Current-native or PSA-synced
    Current-native is the default: the project lives entirely in Current, with no PSA sync — ideal for internal or cross-department work. The synced card — named for your connected PSA, Autotask-synced or ConnectWise-synced — turns on bidirectional sync, with your PSA staying the source of truth for time, billing, and financials.
  4. 4
    Flag it as post-merger integration (optional)
    The PMI toggle marks the project as an M&A / integration engagement so it appears in PMI reporting.
  5. 5
    Click Create project
    The project opens straight into its Overview, ready for phases and tasks.
Tip
Let AI draft it from a statement of work
In the same dialog, "Draft from a SOW" lets you paste a statement of work — Current drafts the phases, tasks, and dependencies for you to review before anything is created. Nothing is saved until you approve the draft.

Start from a playbook

Playbooks are reusable project templates — the fastest way to start a project you've run before (a standard onboarding, a Microsoft 365 migration, an acquisition integration). Open Start a project from a playbook, pick the playbook, and Current clones its phases, tasks, and dependencies into a brand-new project.

  1. 1
    Pick a playbook and name the project
    Choose from your saved playbooks and give the new project its own name.
  2. 2
    Choose a schedule direction
    "From a start date" schedules forward from a kickoff date; "Back from a deadline" schedules every task backward from a go-live date.
  3. 3
    Decide where it lives
    Keep it Current-only, or sync it to your PSA — the partner you attach must already be linked to a company in your PSA if you choose to sync.
  4. 4
    Keep saved assignments (optional)
    Turn this on to restore the playbook's saved per-task assignees, as long as those people are still active in your workspace.
  5. 5
    Attach an acquisition (optional)
    For PMI work, link the project to an existing acquisition or create a new one on the spot.
  6. 6
    Click Create project
    If you chose PSA sync, Current builds the project, phases, and tasks in your PSA automatically — this can take a few passes on a large playbook, and it resumes on its own if the PSA's rate limiting pauses it.

Start from a won quote

When a quote is marked won — in ScalePad Quoter (paired with Autotask) or ConnectWise CPQ (paired with ConnectWise PSA) — it lands in the pending-quotes queue. From there, the conversion wizard can build a project straight from the quote's line items — see "ScalePad Quoter: turn won quotes into projects and charges" or "ConnectWise CPQ: turn won quotes into projects and charges" for the full handoff flow. A quote carries the currency it was priced in, and when that is different from your workspace currency the queue and the wizard flag it and the figures stay exactly as the quote states them.

  • The wizard proposes a project name, partner, and PM from the quote, defaulting to your PSA's synced mode.
  • You choose how the plan gets drafted: from the quote PDF, from a pasted SOW, from a playbook, or day-one tasks only.
  • Four quick onboarding questions (hardware ordering, kickoff call, contract change, hard deadline) shape which day-one tasks get added.
  • A final review step shows a dry run — nothing is created until you confirm.
Note
PSA-synced vs. Current-native
This choice isn't cosmetic. On a PSA-synced project, your PSA stays the source of truth for time and billing, and Current only owns scheduling. On a Current-native project, nothing ever calls the PSA API — no push, no pull. Pick the synced mode for anything that bills through your PSA. See "Project modes: PSA-synced or Current-native".
Was this helpful?