Upgrading from Funnel Vision

If your Dynamics environment has the Funnel Vision Marketing Automation solution (publisher Net-Results, prefix mafvm_), this page is the checklist for replacing it with Paminga for Dynamics 365.

The two solutions coexist without conflict, so there is no downtime: you install the new one alongside the old, move your forms over, let Paminga fill the new columns, and only then remove the old solution. The order matters. Uninstalling Funnel Vision deletes its columns and their data, so everything that reads from them has to be moved first.

Checklist

Work through these in order. Steps 1 and 5 are on Paminga's side; the rest are yours.

1. Paminga confirms the sync-side release is live. The new columns are written by the sync, so the sync has to know about them before anything else happens. Your Customer Success contact tells you when this is done for your account. Do not start step 2 until you have heard.

2. Import Paminga for Dynamics 365 and enter your Paminga API token when the import dialog prompts for it. EU accounts also set the Paminga Panel Base URL after import. Full steps: Import the solution.

3. Add the Paminga tab to your Account, Contact, and Lead forms. Follow Add the Paminga panel to your forms. Leave the old Net-Results tab for now; you remove it in step 6.

4. Add the Paminga Sync role to your existing application user. The Paminga app has the same client ID it always had, so there is no new consent to grant and no new application user to create. In the Power Platform admin center: Environments → your environment → Settings → Users + permissions → Application users → select the Paminga (or Net-Results) app user → Edit security roles → add Paminga Sync → save.

5. Paminga runs the backfill. Once the role is in place, Paminga fills the eight Paminga columns on every synced Contact and Lead from the data Paminga already holds. You do not run anything for this; tell your Customer Success contact when step 4 is done and they will confirm when the backfill has finished.

6. Remove everything of yours that still references the old solution. Views, your own forms, classic workflows, Power Automate flows, business rules: anything you built that reads the old columns. For Lead Score, point each one at Paminga Lead Score. Lead Source has no equivalent column: if a report or flow depends on it, keep its values first (copy them into a column of your own, or export them) and then decide what that report should mean going forward, because the new First Touch Source and Last Touch Source are attribution fields, not the same value under a new name. Do both before step 7, which deletes the old columns. Then clear the places the old solution left its own pieces in. Your edits to a standard form live in an unmanaged layer on top of the old solution's, and that layer keeps the Net-Results tab and script even after the solution is gone, so the uninstall refuses until you remove them. These are the places the old solution left them, including the three that blocked our own uninstall because they are easy to miss:

   • The Account, Contact, and Lead main forms: remove the Net-Results tab (and the mafvm_ columns on it), the mafvm_iframe_script form library, and its OnLoad handler.
   • The User table's main form: remove the Net-Results Credentials tab with the old username and password fields, the mafvm_user_security library, and its handler.
   • The old Information main forms of Account, Contact, and Lead. They are inactive, but they still carry the Net-Results tab and script.
   • The Sales Hub site map: remove the Net-Results group and its two pages.

   Save and publish after each. If the uninstall dialog in step 7 lists a form or a site map as a dependency, this is why. The dialog lists every dependency it finds and blocks the uninstall until they are gone, so you will not remove the solution by accident, but it is faster to clear them deliberately first. Microsoft's guide to reading that dialog: Removing dependencies overview.

7. Uninstall the old solutions, in this order: first Funnel Vision Marketing Automation, then Net-Results Sync for Dynamics 365. In the maker portal, Solutions → select the solution → Delete. Read the box below before you do this; it is not reversible.

8. Optional: tidy up names. Two places can still show the old Net-Results… name. Both are labels only; renaming them changes nothing about the sync.

   • The enterprise application in your Microsoft Entra tenant. This is your tenant's own copy of the Paminga app, and its name is yours to change: rename it under Enterprise applications if you like.
   • The application user in the Power Platform admin center. Go to Environments → your environment → Settings → Users + permissions → Application users, select the Paminga (or Net-Results) app user, and open Details. Select Refresh. Microsoft describes it as syncing the user's name with the name of the registered application, which is Paminga's app registration and is already called Paminga, so this does not depend on renaming the enterprise application above. Microsoft shows Refresh only while the two names differ; if it is not there, there is nothing to update. Microsoft's reference: Manage application users in the Power Platform admin center.

What the uninstall deletes

Deleting a managed solution removes every component it installed and the data in them. For Funnel Vision Marketing Automation that means:

• The mafvm_ Lead Score and Lead Source columns on Contact and Lead, together with every value stored in them
• The per-user Net-Results username and password fields
• The four Net-Results tabs on your forms
• Six web resources and the Net-Results sitemap group

Standard sitemap groups the old solution had removed come back on their own.

The lead score is rebuilt into Paminga Lead Score by the backfill in step 5, from Paminga's own data, so it does not depend on the old column. Lead Source has no Paminga equivalent: Paminga for Dynamics 365 carries the same attribution fields as the Salesforce package (first and last touch source and marketing channel), not the old original-visit lead source. If you need the old Lead Source values for reporting, export them from Dynamics before step 7. There is no way to recover them afterward.

Net-Results Sync for Dynamics 365 contains only the security role of the same name. Uninstalling it deletes that role and removes it from your application user, which is why step 4 gives the user the Paminga Sync role first. It has no other dependencies.

After the Switch

• The Paminga panel on each record replaces the old Net-Results iframe, with the tabs and permissions you chose under Choose what the panel shows
• Lead score now lives in Paminga Lead Score. Paminga Most Recent Visit Date and the six first- and last-touch columns (date, marketing channel, source) give you visit and attribution data you did not have before. The old Lead Source is gone; First Touch Source and Last Touch Source are the attribution alternatives, not a rename of it
• The sync itself is unchanged: same application user, same field mappings, same hourly down sync

If anything on the checklist does not go as described, stop and email support@paminga.com before continuing to step 7.