Save the customizations

Save customizations

Only some of the customizations made to IBM Connections 4.5 application files and custom fields are preserved by the migration commands...

lc-export
lc-import

Files that need to be migrated manually...

Customization Description Automatically migrated Migrate manually
User interface Includes:

customized CSS
JSP
HTML
labels and strings

Customized string files are preserved in the customization directory but we might need to rename some string files to match new Java and Dojo package names in Connections 5.0.
Custom CSS files are preserved in the customization directory but update them to match the new One UI version in Connections.
Partially. Yes.
Template configuration Manual post-migration steps might be required, Partially. See the post-migration steps.
Header and Footer The customized header and footer are preserved in the customization directory, which is not migrated. Update the customized header and footer to match the new layout and functionality of Connections 5.0. No. Yes.
Email notification templates Email notification templates have been translated from JSP to FreeMarker.
Merge existing customizations with the new Notification templates in...
profile_root/Dmgr01/config/cells/cell_name/LotusConnections-config/notifications

If a global customization exists for all emails, then you only need to customize the shared resources. If JSP templates were customized in the 4.5 customization folders, then we can remove them.
No. Yes.
Blog themes
Partially. Yes.
Community themes The default Communities themes are migrated automatically. Redefine any custom theme. Yes Redefine any custom themes.
Business cards The Links and Actions attributes of business cards are migrated when LotusConnections-config.xml, and profiles-config.xml are migrated. Link definitions defined as attributes to each service in the LotusConnections-config.xml file are migrated to the new LotusConnections-config.xml file. The photo and contact information in business cards is migrated from profiles-config.xml in 4.0 to the new businessCardInfo.ftl FreeMarker Template Language file in 5.0. Other elements in profiles-config.xml are migrated to the new profiles-config.xml file. Manual steps may also be required to migrate profile customizations for business cards from 4.5 Yes. Partially.
Security role mappings Redefine the security role mappings. No. Yes.
service-location.xsd Customized extended service names are not migrated. Copy any customized XSD elements to the 5.0 service-location.xsd file. Partially. Yes.
profiles-policy.xml Copy the 4.5 version of the profiles-policy.xml file to the 5.0 deployment, overwriting the 5.0 version of the file. No. Yes.
validation.xml Redefine customized Profile field validation settings. No Yes.
JavaScript The file path and contents of JavaScript string customizations have changed and require manual migration. The ui-extensions framework is deprecated in 5.0 so we must manually migrate the 4.5 JavaScript customizations. No. Yes

Parent topic:
Update and migrate

Related:
Post-migration steps for profile types and profile policies
Customizing
User interface customization
Connections customization best practices
Back up IBM Connections DBS and file systems
Specify a custom field as required and declaring maximum field length
Post-migration tasks
Security role to user or group mapping

Customization	Description	Automatically migrated	Migrate manually
User interface	Includes: customized CSS JSP HTML labels and strings Customized string files are preserved in the customization directory but we might need to rename some string files to match new Java and Dojo package names in Connections 5.0. Custom CSS files are preserved in the customization directory but update them to match the new One UI version in Connections.	Partially.	Yes.
Template configuration	Manual post-migration steps might be required,	Partially.	See the post-migration steps.
Header and Footer	The customized header and footer are preserved in the customization directory, which is not migrated. Update the customized header and footer to match the new layout and functionality of Connections 5.0.	No.	Yes.
Email notification templates	Email notification templates have been translated from JSP to FreeMarker. Merge existing customizations with the new Notification templates in... profile_root/Dmgr01/config/cells/cell_name/LotusConnections-config/notifications If a global customization exists for all emails, then you only need to customize the shared resources. If JSP templates were customized in the 4.5 customization folders, then we can remove them.	No.	Yes.
Blog themes		Partially.	Yes.
Community themes	The default Communities themes are migrated automatically. Redefine any custom theme.	Yes	Redefine any custom themes.
Business cards	The Links and Actions attributes of business cards are migrated when LotusConnections-config.xml, and profiles-config.xml are migrated. Link definitions defined as attributes to each service in the LotusConnections-config.xml file are migrated to the new LotusConnections-config.xml file. The photo and contact information in business cards is migrated from profiles-config.xml in 4.0 to the new businessCardInfo.ftl FreeMarker Template Language file in 5.0. Other elements in profiles-config.xml are migrated to the new profiles-config.xml file. Manual steps may also be required to migrate profile customizations for business cards from 4.5	Yes.	Partially.
Security role mappings	Redefine the security role mappings.	No.	Yes.
service-location.xsd	Customized extended service names are not migrated. Copy any customized XSD elements to the 5.0 service-location.xsd file.	Partially.	Yes.
profiles-policy.xml	Copy the 4.5 version of the profiles-policy.xml file to the 5.0 deployment, overwriting the 5.0 version of the file.	No.	Yes.
validation.xml	Redefine customized Profile field validation settings.	No	Yes.
JavaScript	The file path and contents of JavaScript string customizations have changed and require manual migration. The ui-extensions framework is deprecated in 5.0 so we must manually migrate the 4.5 JavaScript customizations.	No.	Yes