Implementation Guide

Small Business Project Manager Pro Implementation Guide

Installation, dependencies, licensing, configuration, integrations, upgrade and go-live guidance for Small Business Project Manager Pro.

8 chapters192 wordsPublic guide
Complete online manual

This guide covers implementation, configuration, daily use and troubleshooting for Small Business Project Manager Pro.

Purpose

This guide is for administrators, implementers and agencies deploying Small Business Project Manager Pro version 0.5.9.

Requirements and dependencies

  1. Requires Project Manager Free
  2. Activate the Pro licence
  3. Keep Free active
  4. Configure AI provider where used
  5. Validate resource and automation settings

Installation

  1. Back up the WordPress files and database.
  2. Upload the plugin ZIP through Plugins > Add New > Upload Plugin.
  3. Activate required foundation plugins first.
  4. Activate this plugin and complete its setup screens.
  5. For licensed editions, activate the licence before enabling premium modules.

Configuration

Review roles, permissions, email settings, page assignments, integrations and data-retention settings before importing production data.

Implemented feature areas

  • Everything in Free
  • Gantt chart
  • Calendar view
  • AI project builder
  • Advanced templates
  • Resource capacity and workload
  • PRINCE2-aligned planning
  • Automation hooks
  • WhatsApp companion integration

Upgrade and rollback

Use staging for major upgrades, retain a tested backup and never remove a required Free foundation while its Pro or Agency add-on is active.

Go-live checklist

  1. Test the primary workflow end to end.
  2. Confirm emails and scheduled actions.
  3. Check mobile and staff/customer access.
  4. Verify licences and optional companion plugins.
  5. Document the responsible administrator.

Troubleshooting

If activation fails, confirm PHP and WordPress compatibility, dependency versions and licence status. Temporarily disable unrelated plugins only on staging and inspect the WordPress debug log for the exact error.