Task migration from Advance to Slate

Overview of Slate Tasks

Slate thinks of tasks a little differently than Advance. Here are the main changes we'll experience as we begin to use Slate Tasks:

  • Slate Tasks are meant to remind someone specific to do something rather than be a record of things that have been done.
  • Slate Tasks are easily visible to the assigned person. If an additional manual step is taken, specific tasks can be made visible to a team of people. However, tasks aren't easily visible outside of those two options.
  • Slate Tasks are assigned to one person and/or one team (i.e. Stewardship, or Grants Office), but cannot be assigned to two or more specific people. (For example, a task could be assigned to "Carla Thomas" or to "Slate Administrators," but that same task could not be assigned to Carla and Denise but not Iris.)
  • Slate Tasks cannot be attached to a Proposal (called an Opportunity in Slate). Any Proposal Tasks in Advance have to be specifically converted so that they appear in appropriate places in Slate (Grants, Planned Giving, and Research have all worked with the implementation team to convert their Proposal tasks, see below)
  • Slate Tasks cannot be assigned to a Prospect Record (since prospect records do not exist in Slate), so instead all Prospect tasks in Advance will be attached to the primary Person or Org associated with our current Advance Prospect records.

Which Tasks are Migrating from Advance To Slate?

For Everyone

  • Pending and In Process tasks attached to Advance Entity records and assigned to current staff members
  • Pending and In Process tasks attached to Advance Prospect records and assigned to current staff members.
    Note: Because Prospect records aren't separate records in Slate, these tasks will be attached to whichever associated Entity record is marked as the Primary record on the Advance Prospect record.

By Special Arrangement

  • Tasks attached to Allocations in Advance:
    • Current plus 5 years of historical tasks
  • Tasks attached the Proposals in Advance:
    • Planned Giving (coded IPG, PGS, PGP, or assigned to Laurel, Keir, Christian, or former team members) - current and historical
    • Grants (coded PAN, PAR, CNT, PGE, PGM, PPD, PSR, ICF) - current and historical
    • Research/Gift Officer Next Steps for Horizon Report (coded IRR or IIH) - current only  (Pending/In-Process)
  • Tasks attached to Prospects in Advance
    Note: Because Prospect records aren't separate records in Slate, these tasks will be attached to whichever associated Entity record is marked as the Primary record on the Advance Prospect record.
    • Planned Giving (coded IPG, PGS, PGP, or assigned to Laurel, Keir, Christian, or former team members) - current and historical
    • Grants (coded PAN, PAR, CNT, PGE, PGM, PPD, PSR, ICF) - current and historical
    • Everything Else:   current only (Pending/In-Process assigned to current staff members)
  • Tasks attached to constituent Entities in Advance
    • Planned Giving (coded IPG, PGS, PGP, or assigned to Laurel, Keir, Christian, or former team members) - current and historical
    • Grants (coded PAN, PAR, CNT, PGE, PGM, PPD, PSR, ICF) - current and historical
    • VATs - current and historical
    • Everything Else:  current only (Pending/In-Process and assigned to current staff members)

Questions?

Don't hesitate to contact us! You can email dev-info-services.group@carleton.edu or you can use this form to submit your question to the Slate Implementation Team.

Was this helpful?
0 reviews
Request Service Print Article

Related Services / Offerings (1)

Request help using Slate or report a Slate issue.