How do you reconcile pipeline coverage for renewal and expansion on Dynamics 365 without another point solution when data warehouse in Snowflake?

Reconciling pipeline coverage for renewal and expansion in Dynamics 365 without introducing another point solution, while leveraging a Snowflake data warehouse, involves structuring your Dynamics 365 data, establishing a robust ETL process into Snowflake, performing sophisticated transformations within Snowflake, and visualizing the results using a native Microsoft BI tool like Power BI.

This approach relies on Dynamics 365's extensibility for data capture, Snowflake's analytical power, and Power BI's integration capabilities to provide a unified view.

Dynamics 365 Data Model for Renewal and Expansion

To effectively track renewal and expansion opportunities, Dynamics 365 requires specific configurations:

1. Opportunity Types: Implement distinct opportunity record types or a custom field (Opportunity Type) with values such as "New Business," "Renewal," and "Expansion." This segregation is crucial for accurate reporting.
2. Custom Fields:

• Renewal Opportunities: Add fields like Original Contract ID (lookup to a Contract entity), Current Contract End Date, Renewal Probability, and Original Annual Recurring Revenue (ARR).
• Expansion Opportunities: Include Parent Account ID, Current ARR, Expansion Type (e.g., cross-sell, upsell, additional seats), and Expected Incremental ARR.

1. Contract/Subscription Entity: Ensure a Contract or Subscription custom entity exists, linked to Accounts, storing Start Date, End Date, Current ARR, and Renewal Date. This entity serves as the source of truth for addressable renewal revenue.

4.