Ctrlk
Contact Us
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Partnerships and Coalitions as Legacy Modules

Understand what changed for the Partnerships and Coalitions modules now that Partners supersedes them.

The Partners module replaces Partnerships and Coalitions. Nothing is deleted and nothing stops working — but the two older modules are now labeled as legacy, and new organizations do not get them at all.

What Changed

In the Engage menu. Once the Partners module is on and your organization still has at least one of the older modules enabled, Partnerships and Coalitions move beneath a Legacy heading at the bottom of the Engage menu.

On records with a Partners section. Modules that link to partners can carry both the old section and the new one. When both are on, the older section's step reads Partnerships (Legacy) so the two are distinguishable, and the new one reads Partners. See Add Partners.

In exports. The Partnerships and Coalitions exports pick up a (Legacy) suffix in their file names. Worksheet names inside the files are unchanged, so existing downstream scripts keep working.

On dashboards. The two legacy dashboard panels are renamed Partnership & Coalition Characteristics (Legacy) and Partnership & Coalition Assistance & Relationship (Legacy). A new Partners and Contacts panel group sits beside them. See Panels.

For new organizations. Partnerships and Coalitions are off by default. Existing organizations keep whatever they had enabled.

NOTE: Your legacy Partnership and Coalition records are untouched. They remain readable, editable, and exportable for as long as the modules are enabled for your organization.

Running Both at Once

During a transition you can have the legacy modules and Partners on at the same time. A record that has both sections enabled shows both, so you can keep reporting the old way while you build out the new one.

TIP: Existing organizations do not get the new Partners sections on their records automatically — adding a brand-new workflow step to every existing record would drop its completion percentage. An Organization Administrator turns each one on per module from Organization Settings.

Migrating Legacy Data

You can bring your Partnership and Coalition records into Partners yourself, from the PEARS interface. The process has three steps — export a migration workbook from the legacy list, review it in Excel, then import it through the Partner Importer.

The two structures do not map one-to-one, so the workbook is where you make the judgment calls before any records are created:

  • A Partnership stores one record per reporting period, so the many records describing one real-world partner collapse into a single Partner with a Partner Report for each period.

  • Records sharing the same partner name at the same site are merged into one Partner.

  • Start and end dates are derived from the reporting periods present in the export.

  • Assistance received and provided become partner activities; linked action plans, jurisdiction level, and uploads carry across.

  • Coalition members become CRM contacts linked to the Partner.

Nothing is deleted — the legacy records stay in place after the import.

TIP: Running a migration requires the Organization Administrator or Data Manager role. See Migrate from Partnerships and Coalitions for the full walkthrough.

Related Documentation