WordPress is built on the idea of freedom. Freedom to move, to modify, and to choose who maintains your website.
At Faeb, we respect that principle. While we adapt WordPress at the core level to meet our security and performance standards, we do so in a controlled, documented, and reversible manner. Every change we apply follows defined steps and can be rolled back or re-orchestrated without leaving dependencies behind.
This approach exists for one reason: to ensure clients are never locked into the Faeb ecosystem.
A Migration System Designed Around Freedom
To preserve portability, we have developed a proprietary migration system that supports both directions of movement.
- Migrating into Faeb from a traditional WordPress setup is designed to be smooth and non-disruptive.
- Migrating out of Faeb back to a standard WordPress environment is equally supported and handled with the same care.
In both cases, the goal is continuity, stability, and clarity—not dependency.
In-Migration: Moving Into Faeb
When we accept a client who already has a WordPress website, we manage the entire migration process.
This includes:
The process is handled end to end by our team. Clients are not required to coordinate technical steps or make configuration decisions. The transition is designed to be predictable and interruption-free.
Out-Migration: Moving Out of Faeb
If a client chooses to leave Faeb, we ensure their WordPress installation is returned to a standard, independent state.
The migration is handled by us and structured to remove all Faeb-specific dependencies. During this process, we ensure the following:
- The WordPress core is reverted to its original, unmodified state, restoring universal compatibility and independence
- Faeb Layers is fully removed, and clients are free to adopt any third-party security solution of their choice
- Any functions disabled for security or performance reasons, such as XML-RPC, are restored, allowing clients or future developers to manage them according to their own preferences
- Design layouts are migrated to Elementor so content remains easily editable and transferable
- The active theme is reverted to either Hello Elementor or a recent official WordPress theme, based on client preference
- The database is cleaned, normalized, and exported for portability
After migration, the website does not require any Faeb tooling to function.
For delivery, we provide a single-file backup and recommend standard tools such as WPvivid Backup for import, ensuring compatibility with typical WordPress environments.
Why We Don’t Endorse Lock-In
Lock-in contradicts the core philosophy of WordPress. It restricts movement, limits choice, and shifts control away from the site owner.
Faeb does not operate that way.
Clients can enter or exit the Faeb ecosystem at any time. We actively support both transitions and handle them ourselves to ensure consistency and peace of mind.
The objective is not to retain clients through dependency.
It is to earn retention through quality, transparency, and trust.
Freedom is preserved in both directions, by design.
Razique – Founder, Faeb