Linked Data Frontend (LDF) Migration Guide

09/04/2026

This guide outlines the manual migration process for the PoolParty Linked Data Frontend. With the release of PoolParty 10, the platform has become fully dockerized and cloud-native. This migration guide is required to bridge the transition from the local file system to the new containerized volume structure.

The LDF architecture remains based on the Model-View-Controller (MVC) pattern using Velocity Templates, allowing for high levels of UI customization.

Before beginning the migration, ensure the following conditions are met:

PoolParty 10 is installed and the underlying data migration has been completed. Refer to the PoolParty 10 Installation Guide for more information on how to install PoolParty from scratch. Alternatively, refer to our PoolParty 2025 R2 (9.7) to PoolParty 10 Migration Guide to migrate an existing PoolParty installation.
A backup of existing LDF templates from PoolParty 9.7.1 exists and can be accessed.
Path: /opt/poolparty/data/frontendRoot
A backup of the default PoolParty 10 LDF templates from the new Docker container has been created for reference.
Path: /var/lib/poolparty/data/frontendRoot
A new host directory (e.g., ldf_data) has been created to act as the bind mount volume for the Graph PoolParty 10 container.

Follow these steps to move your custom templates to the new environment.

Copy the contents from your source directory to the new target directory on the PoolParty 10 host.
```
cp -r /opt/poolparty/data/frontendRoot ldf_data
```

Set the appropriate ownership and permissions to ensure the Docker container can access the files.

# Set ownership to the poolparty user
sudo chown -R poolparty:poolparty ldf_data

# Set directory and file permissions
sudo chmod -R 755 ldf_data

Ensure the ldf_data directory contains the expected sub-folders. The custom folder will only exist if UI modifications were previously made.
```
drwxr-xr-x 3 poolparty poolparty   17 Mar 23 17:49 custom
drwxr-xr-x 9 poolparty poolparty  189 Mar 23 17:49 default
```
Modify your docker-compose.yaml to bind mount the host directory to the container. In this approach, a privileged user configures a bind mount to map a specific local directory from the host server to the Docker container. This ensures users can interact with and modify only the designated local directory on the host without needing elevated permissions within the Docker container itself.
Add the following to the poolparty service block:
```
services:
  poolparty:
    # ... other configurations ...
    volumes:      
      - type: bind
        source: ./ldf_data
        target: /var/lib/poolparty/data/frontendRoot
```

Apply the changes by restarting the PoolParty service.

docker compose -f docker-compose.yaml -f addons.yaml up -d poolparty

Test the frontend by navigating to http(s)://<server_url>/<project_title>.html.
As of version 10.1, PoolParty enforces Content Security Policy (CSP) headers. Templates from 9.7.1 and earlier versions sometimes contain inline JavaScript or CSS that violates these policies. Inspect your .vm files and external assets and refer to our guide on Content Security Compliance for more information.
Because the default template was updated for the PoolParty (Graph Modeling) 10 rebranding, templates migrated from 9.7.1 will retain the legacy visual identity. To adopt the new Graph Modeling styles, compare your migrated templates against the reference backup.

In this section: