Recovering Source From a SourceGuardian-Protected Perfex CRM

Perfex CRM is a self-hosted, CodeIgniter-based customer relationship management system sold as a licensed product, and it has a large ecosystem of third-party modules for things like SMS, accounting integrations, and industry-specific workflows. Businesses run Perfex on their own servers, customize it heavily, and depend on it for invoicing, projects, tickets, and client management. When a Perfex install or a module was shipped with SourceGuardian-encoded PHP, it works, but the readable source needed to customize or audit it is out of reach.

If you own the Perfex license and the custom code, or you are authorized in writing to maintain it, recovering readable PHP for the parts you own is a legitimate task. This guide explains the common scenarios, how Perfex is structured, what to gather, and what recovered source gives you. It does not cover how recovery works internally.

Where Perfex Owners Get Stuck

Self-hosted CRMs accumulate customization. A business buys Perfex, hires a developer to build custom modules for its workflow, and over time the CRM becomes central to operations. Two problems commonly arise. First, a custom module built by a contractor was delivered SourceGuardian-encoded and the contractor is gone, leaving the business unable to maintain a module it paid for and owns. Second, a business needs to audit its own heavily customized install for security or compliance and cannot read the encoded portions.

Because Perfex is self-hosted, the owner is responsible for keeping it running on a modern PHP version and a secure server. An encoded custom module that breaks on a PHP upgrade, or that a security review flags as unreadable, becomes a real operational risk.

Confirming You Are Authorized

Be precise about what you are entitled to recover. You may recover custom modules and code you own or commissioned as work-for-hire, and code you are permitted to maintain under a written agreement. The Perfex core itself is a licensed commercial product from its vendor; if your need concerns the core or an official product, contact the vendor or the module author first. This guide assumes you are recovering custom or owned code, and you should keep proof of ownership for it.

How Perfex CRM Is Structured

Perfex is built on CodeIgniter, so its layout will feel familiar if you know that framework. A Perfex install generally includes:

• application/, the CodeIgniter application with controllers/, models/, libraries/, and helpers/ that make up the core CRM and its customizations.
• modules/, where third-party and custom modules live, each in its own subdirectory with its own controllers, models, and an install file.
• application/views/ and module views/, the presentation layer, usually readable.
• application/config/, configuration for the app.
• uploads/ and asset directories, which hold data and static files, not logic.

The encoded logic worth recovering is the PHP inside your custom modules and any custom application code you own. Each Perfex module typically has an install.php or module bootstrap, hooks that register with the CRM's action and filter system, and controllers exposed under the admin area.

What to Gather Before You Start

For a module, submit the entire module directory from modules/, not a single file. Perfex modules register hooks, define menu items, and wire controllers to models, so recovering the whole module keeps those pieces consistent. If the customization spans the core application, gather the specific custom files you own rather than the licensed Perfex core.

Note the Perfex version, the PHP version your server runs, and the module version if the module declares one. Keep the module's views/, language files, and assets as they are, since they pair with the recovered PHP. Our SourceGuardian decoder handles owner-authorized recovery of the encoded PHP in your custom modules.

What Recovered Source Looks Like

Recovered Perfex module code is readable PHP that follows CodeIgniter and Perfex conventions. You will see the module's registration and hook calls, the controller classes that back the admin pages, the models that read and write CRM data, and the helpers the module relies on. That is enough to trace a feature from its menu entry to its controller to the database and to change how it behaves.

Realistic expectations apply. Comments are typically not recovered. Variable names inside methods may be normalized to clear names. The hook registrations, controller actions, model queries, and overall structure are faithful, which is what makes the module maintainable and auditable again.

Getting Your CRM Customizations Back Under Control

With readable source recovered, put the module or custom code into version control immediately. Stand up a staging copy of your Perfex install and activate the recovered module there, then walk through its admin pages and confirm its hooks fire and its data operations work as expected.

Now you can do the work that prompted recovery: fix PHP deprecations that threaten a server upgrade, address issues a security audit raised, and adapt the module to a newer Perfex release. Because Perfex is CodeIgniter under the hood, our PHP decompiler page is a useful reference for how the recovered PHP structures map to the framework you are maintaining.

FAQ

Can I recover the Perfex core itself? This service is for code you own or are authorized to maintain, such as custom modules and commissioned code. The Perfex core is a licensed commercial product; for anything concerning the core, contact the vendor. Recover your own custom modules and code.

A contractor built and encoded a module for us. Can we recover it? If your business owns that module as work-for-hire, typically yes. Keep the contract or invoice that establishes ownership. If the module is instead a product licensed from a third party, contact that author first. See our FAQ.

Do I need to recover the module's views and language files? Usually not. Views and language files are commonly readable already. Only the encoded PHP controllers, models, and helpers need recovery, and they pair with your existing views.

Will the recovered module still register its hooks correctly? Yes. Recovered PHP keeps the same function and class names, so the module's hook and menu registrations continue to work once the module is reinstalled in your Perfex install.

What does recovery cost for a module? Cost depends on the number and size of encoded PHP files in the module. Our pricing page explains the tiers.

If you own or are authorized to maintain custom Perfex CRM code, start with a free trial or create an account to recover readable source for your system.