Confirm the current application requirements and identify the content/configuration paths that must be backed up. Database backups alone do not protect a flat-file blog.

Use the project's current supported release information and the requirements shown for the package you select. If Softaculous offers an older or unsuitable build, follow the current vendor installation process or ask us to confirm a suitable environment. Do not enable an unsupported PHP runtime simply to reproduce an old tutorial.

1. Back up any existing site at the destination. Choose an empty directory or a separate staging hostname for a new installation; never approve overwriting a working site without a migration plan.
2. Open Softaculous where your hosting service includes it. In cPanel, search for Softaculous Apps Installer. In SiteWorx, use Hosting Features > Softaculous where that integration is enabled.
3. Find HTMLy and review the package and requirements before selecting Install. Select the correct HTTPS domain. Leave In Directory empty only when the empty domain root is the intended destination.
4. Complete the application-specific fields and a strong administrator credential stored in a password manager. Supply a reachable administrative email where requested. Review the backup destination, update choices and documented content/configuration directories. HTMLy content is stored in files, so a database-only backup is not a recovery copy of this blog.
5. Start installation once and wait for the completion result. Record the public and administration URLs. Where this application needs the publisher's own deployment process, complete that process instead of forcing an outdated installer package.

Set the blog identity, public URL and author access. Create a post with an image and review the generated links. Keep themes and plugins limited to versions compatible with the current release.

Select one older HTMLy post that includes a local image and open both the post and the image after the trial move. Check the image URL in the browser, not just whether the page looks correct while the old server remains online.

1. Confirm the destination contains the actual media file in the expected path.
2. Compare the blog's configured base URL with the public HTTPS address.
3. Inspect a category or feed entry that references the same post.
4. Verify the private recovery archive includes the post, media and configuration files needed to reproduce the result.

If the image still loads from the old host, correct the supported path or content setting in the trial copy before retiring the source. Do not broaden permissions across the whole installation to repair a URL mismatch. Test another older and newer post after the change.

Test a published post, feed and uploaded media as a visitor. Inspect an off-account backup and confirm it contains content and configuration files.

If text appears but images fail after moving the site, compare the media paths and base URL. Correct ownership and narrowly scoped write permissions rather than making the full installation writable to everyone.

Keep files and data together in your recovery plan, test application updates in a copy when practical, and review logs after deployment. If installation fails, record the exact error, selected application/PHP versions and destination path before retrying.

• Choosing and managing applications with Softaculous
• Migrating an older blog to WordPress or a current publishing platform
• Creating Web Hosting backups and planning a restore
• Changing PHP versions, extensions and application limits
• Installing Dotclear and checking the first setup

• Softaculous installation workflow
• Softaculous blogs catalogue