FormKiQ is an Alfresco alternative when your next document system needs to run in your AWS account, connect to business applications through APIs, and support governed document workflows. Start by deciding whether you are replacing an active repository, retaining historical records, or doing both.
For active work, select the relevant packaged Business Solution or connect document services to your existing application. For historical records, the Legacy System Archive and Access solution delivers searchable archive files, source context, reconciliation, and continuing access and retention workflows.
Plan an Alfresco migrationWhen replacing Alfresco is worth evaluating
A replacement makes sense when it improves a specific business or operating requirement. Examples include connecting document retrieval to a new application, retiring an installation retained for historical access, or adopting customer-managed AWS operations.
Alfresco already provides APIs and a configurable content model. Its public REST API guide documents repository operations and supported extension boundaries. Evaluate the application and operating model your team needs; API availability alone does not distinguish the products.
| Decision | FormKiQ approach | What to compare with your Alfresco estate |
|---|---|---|
| Active document work | Packaged applications for contracts, claims, cases, records, and other supported workflows; APIs for existing applications. | Users' actual tasks, custom screens, integrations, and dependencies on current repository behaviour. |
| Historical access | A dedicated archive application that keeps source records and retrieval context after the original system is retired. | Which files need occasional access, and which still participate in active business processes. |
| Deployment and operations | AWS resources in the customer's account for customer-managed deployments; other operating models have edition and engagement boundaries. | Account ownership, update responsibility, monitoring, recovery, and support under the current and proposed arrangements. |
| Cost | Base licensing, selected modules, implementation, AWS usage, and any external-provider fees. | Current licensing, infrastructure, support, customisation maintenance, migration effort, and ongoing operation using the same workload assumptions. |
Published customer evidence
RGF Staffing Belgium moved more than 20 million documents
Integration Architect Micha Van Nijen's December 2025 account describes replacing Alfresco with FormKiQ, using a phased AWS migration and updating application references. This establishes a customer example at that scale; it does not establish a standard migration duration or cost reduction for another organisation.
Read the RGF migration snapshot · Read the customer's original account
Illustrative decision · fictional purchasing team
Retire a repository while keeping historical orders accessible
A purchasing team has moved new orders into an ERP, while staff still open Alfresco to retrieve old agreements and invoices. Those documents need source references, controlled access, and continuing retention review; they do not need to recreate the old purchasing application.
- 1 · Scope
Separate active and historical work
Identify the historical order files and their obligations. Keep current order processing in the ERP and define its link to the archive.
- 2 · Validate
Accept an archive file
The archive application connects the original order reference, mapped documents, reconciliation results, and acceptance evidence. Reviewers resolve exceptions before acceptance.
- 3 · Retrieve
Open the historical evidence
Authorised staff retrieve the accepted file through the archive or the agreed ERP integration, with ongoing access and retention controls.
Inspect the Legacy System Archive and Access workflow. Source mappings, ERP links, access rules, and retention policies are configured for the organisation.
When FormKiQ fits
Your team wants an AWS document platform with packaged business applications, explicit account ownership, APIs, and configurable workflows. You can define the source-to-target mappings and evaluate the operating responsibilities alongside the application.
When keeping Alfresco may fit
Your existing implementation meets the workflow and operating requirements, or the value of a replacement does not justify migrating its custom applications and integrations. An upgrade or a narrower archive project may address the immediate problem with less transition work.
Replacement evaluation checklist
- Demonstrate one representative user journey, including an exception and a denied-access case.
- Inventory content types, custom properties, versions, permissions, holds, workflows, and integrations.
- Choose active workflow replacement, historical archive access, or a staged combination.
- Confirm the edition, modules, delivery scope, and operational responsibilities in the proposed deployment.
- Price both options against the same storage, processing, support, and migration assumptions.
- Agree reconciliation, cutover, recovery, and source-retirement criteria before production import.
Choose around the work that must continue
A useful Alfresco replacement preserves the documents and business context people need, while improving the application or operating model that prompted the change. Validate that outcome in a bounded pilot before expanding the migration.
Migration planning and validation · Customer-managed AWS responsibilities · Edition and module comparison
Review your Alfresco replacement scope
Bring a representative file, its business process, and the dependencies you need to preserve. We can review the appropriate application, migration path, and deployment model.
Book a replacement review