---
title: "Migrating from PCF PRO to Power Custom Fields"
canonical: "https://support.appfire.com/space/PSJ/15487207/Migrating%20from%20PCF%20PRO%20to%20Power%20Custom%20Fields"
format: markdown
---
> Macro (button-handy)



  


> ℹ️ This page is intended for users who already use **Power Custom Fields PRO** and **Power Custom Fields** simultaneously.
> ℹ️ 
> ℹ️ If you are a first-time user of Power Custom Fields, feel free to skip this page.

## Meet Power Custom Fields

As part of our revised strategy, we have moved all custom field functionality into one Power Custom Fields app, your ultimate go-to plugin. This change consolidates our offering and lays the foundation for upcoming enhancements.

### Notes for Power Custom Fields PRO users

Fields defined by Power Custom Fields PRO will continue to work like those defined in Power Custom Fields. No changes are expected or intended.

If you already have Power Custom Fields PRO and are installing Power Custom Fields, consider the following precautionary measures:

1. You are entitled to a PCF license with a valid PCF PRO license.
  1. Contact us, and we'll help migrate your license from PRO to PCF.
2. <span style="color: #333333">All custom fields defined by PCF PRO </span><span style="color: #333333">**will be migrated automatically**</span> along with their configuration.
  1. Note that this step cannot be reversed easily.
    1. You must contact support and reverse it by running specific SQL scripts on your database.
    2. This process is not recommended.
3. Migrating your PRO license is recommended, as new improvements and maintenance will only be implemented into PCF.
4. Both PCF PRO and PCF will continue to function in parallel. However, we **strongly recommend uninstalling PCF PRO** at your earliest convenience because the migration task happens only once.
5. **Do NOT create more custom fields via PCF PRO**. All PCF Pro functionality exists in PCF.
6. After installing PCF and uninstalling PCF PRO, we strongly recommend restarting Jira and performing a Jira re-index.

### Troubleshooting

PCF and PCF PRO work in parallel, allowing you to switch editions easily. However, if you encounter problems during your migration, here's a list of known issues.

| Symptom | How to solve | Explanation |
| --- | --- | --- |
| You have have both Power Custom Fields and Power Custom Fields PRO and cannot update the configuration of the existing fields.<br>When you click the referring link, a 404 error appears.<br>![image](media://f8fcb82a-f94d-4797-9098-e27a8c5d2dda) | 1. Uninstall the PCF PRO plugin.
2. Perform a disable/enable cycle in PCF.<br>We recommend the disable-enable cycle on  PCF to be sure the new add-on is in effect. Another option for you is to restart Jira **after** you uninstall PCF PRO. | All fields from PCF PRO are migrated and this might cause certain conflicts between the two versions. |
| LOG custom field is missing / not rendered | Remove the custom field. It is no longer provided by Power Custom Fields. | There are better options to deal with the log at this moment. Specifically, SIL Manager’s new runner and log viewer. Stay tuned! |
| After un-installing Power Custom Fields PRO, the migrated fields work perfectly but the administration pages return the 404 error (not found). The following or similar exception text appears in the logs:<br>* *<span style="color: #333333">*org.picocontainer.injectors.AbstractInjector$UnsatisfiableDependenciesException: *</span>* *<br>* *<span style="color: #333333">*com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.view.EditSilOptionsCFConfig has unsatisfied dependency *</span>* *<br>* *<span style="color: #333333">*'interface com.keplerrominfo.jira.commons.hostapp.JMUserServices' for constructor 'public com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.view.EditSilOptionsCFConfig(*</span>* *<br>* *<span style="color: #333333">*com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.ConfigurationParametersService,*</span>* *<br>* *<span style="color: #333333">*com.keplerrominfo.jira.plugins.keplercf.smartselect.optionscf.config.ds.DataSourceFactoryRegistry,*</span>* *<br>* *<span style="color: #333333">*com.keplerrominfo.warden.addon.LicenseStatusService,*</span>* *<br>* *<span style="color: #333333">*com.keplerrominfo.jira.commons.user.CurrentUserHelper,*</span>* *<br>* *<span style="color: #333333">*com.keplerrominfo.jira.commons.hostapp.JMIssueServices,com.keplerrominfo.jira.commons.hostapp.JMUserServices)' *</span>* *<br>* *<span style="color: #333333">*from org.picocontainer.DefaultPicoContainer@15e86fad:*</span>* *<br>* *<span style="color: #333333">*1<[Immutable]:com.atlassian.jira.component.pico.CachingMutablePicoContainer@737befef*</span>* *<br>* *<span style="color: #333333">*        at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:191)*</span>* *<br>* *<span style="color: #333333">*        at org.picocontainer.injectors.ConstructorInjector.getGreediestSatisfiableConstructor(ConstructorInjector.java:110)*</span>* *<br>[ ...... rest of the stack trace removed for brevity .... ] | Restart Jira<br>- or -<br>Restart Power Custom Fields (execute a Disable - Enable in the 'Manage Add-ons' Jira administration page). | This error affects Jira servers randomly, and currently, there isn’t a fix.<br>Some Spring beans references exposed by the Warden and SIL Engine companion add-ons are lost. Normally un-installing PCF PRO shouldn't touch the existing SIL Engine and Warden add-ons, but it does occasionally happen.<br>We are working on a solution. |

  


> ℹ️ ### Additional Assistance
> ℹ️ 
> ℹ️ For additional assistance, open a support request [here](https://appfire.atlassian.net/servicedesk/customer/portal/11).