01Continuity register · 3 checks No history lost Your past invoices keep the original full number (e.g. F-2025-0142) and issue date. Cofactu's VeriFactu hash chain starts clean from your first new invoice, with no collision against the Quipu numbering. 
Migrate from Quipu to Cofactu
without losing a single invoice
Quipu was acquired by Sage in 2024 and the roadmap has cooled off. Bring your clients, products, and invoices to Cofactu by uploading Quipu's Excel export, which Cofactu recognises. Invoices you already issued arrive as historical and aren't resent to AEAT; new ones start the VeriFactu hash chain from scratch.
No card · Reviewable import · History kept apart from new operations
| 01 · Source | Quipu | CSV clients · tax details · XLS invoices · history · CSV products · catalogue and VAT |
|---|---|---|
| 02 · Review | Control gate | 1 Columns recognised · 2 Duplicates set aside · 3 Series confirmed |
| 03 · Destination | Cofactu | History available · New chain prepared · Status: Ready to review |
Source copy kept · Import with preview · Review before issuing
What shouldn't be lost Moving the history doesn't mean
Moving the history doesn't mean
breaking its context.
The move keeps what you need to consult the past and separates new invoices so you can review before continuing.
01Continuity register · 3 checks No history lost Your past invoices keep the original full number (e.g. F-2025-0142) and issue date. Cofactu's VeriFactu hash chain starts clean from your first new invoice, with no collision against the Quipu numbering. 
02Continuity register · 3 checks Zero invoicing downtime Keep invoicing in Quipu while you try Cofactu in parallel. When you're ready, cancel Quipu — Cofactu keeps your data. No cutoff, no forced transition period. 
03Continuity register · 3 checks No lock-in If you ever wanted to go back, you export data per module (clients, invoices, expenses, PDF + XML records) and request a complete account copy. We don't block the exit — transparency runs both ways. One documented path, with a review before importing.
Cofactu does not import through the Quipu API. The guide starts from the exported file and a prior review of its contents.
Documented route
Export from Quipu
- 1 min · File
Export from Quipu
Quipu → Invoicing → Export → Excel. Repeat for Contacts → Export. The Excel export is available on ALL Quipu plans, including Basic. You don't need a Pro plan for this option.
- 1 min · File
Upload the files to Cofactu
Create your free account and, in Invoices, click Import and upload the file. Do the same for contacts from Clients. Cofactu recognises the Quipu format and skips the column step. Before confirming you see a preview of what will be imported.
- 2 min · File
Confirm and go
Review the preview with N invoices + M clients and hit Import. Done. Historical invoices keep their Quipu numbering (e.g. F-2025-0142) and arrive as already issued, without being sent to AEAT.
Scroll
The switch ends when the new system
can already do the work.
These are the capabilities that stay connected after bringing the history over from Quipu.
| 01 | Real VeriFactu from day 1 | Cofactu sends records to AEAT with an official CSV every time you issue an invoice. Post-Sage Quipu has prioritized integrating Sage 50 over its own roadmap — the explained catalog of AEAT errors, automatic detection of a broken hash chain (4171), and 1-click repair are only in Cofactu. |
|---|---|---|
| 02 | Bank reconciliation included | Upload the statement (Norma 43, CSV or Excel — any bank works) and Cofactu matches movements to your invoices and posts the entry in 572. In Quipu, banking is a separate paid module. |
| 03 | Human support with no premium gating | People by WhatsApp and email on every Cofactu plan (including Free). Quipu reserves phone support for the €49/month Premium plan — and standard chat is slower on lower-tier plans. |
| 04 | AEAT forms prepared by channel | Cofactu calculates all seven forms and generates the official file for 303, 111, 115, 190, 347 and 349; form 130 is prepared as a draft. You or your accounting firm file them in the AEAT online office. |
History available to consult · New operations active
Clean chain Your first new invoice opens
Your first new invoice opens
a verifiable chain.
Keep the originals and the supporting documents of the invoices issued from Quipu. Don't issue them again as if they were new operations. Review the series and the configuration of new invoices in Cofactu separately.
- History imported and available to consult
- New records chained and submitted
- Detection of breaks in the chain
| History | Quipu | Keeps its originals |
|---|---|---|
| New genesis | ||
| First new invoice | F-2026-00001 | SHA-256 hash · chained |
| Next record | F-2026-00002 | Previous hash linked |
Illustrative example · Check series and date
The operations that carry on The history arrives. The next tax forms
The history arrives. The next tax forms
are born from your new data.
Cofactu aggregates new invoicing, expenses and withholdings to prepare the supported tax forms from the same system.
Before migrating from Quipu.
Answers on timing, history, numbering and continuity before you confirm the move.
Ask about my case →Are my invoices already sent to AEAT from Quipu resubmitted?
No. Every imported invoice arrives as historical (accepted) and Cofactu never sends it to AEAT, so there are no duplicates. It doesn't carry the AEAT CSV: keep the receipt in your previous software. Cofactu's VeriFactu hash chain starts clean with your first NEW invoice.
Do I lose Quipu's change history or audit log?
Quipu's internal logs stay in Quipu — our importer doesn't extract them. But from the moment of import, Cofactu keeps its own immutable audit log with a hash chain (creation, editing, AEAT submission, and payment events).
Does it work with any Quipu plan?
Yes. Cofactu doesn't use Quipu's API: it imports the Excel export, which is available on every Quipu plan, Basic included.
What happens to my OCR expenses from Quipu?
Cofactu has its own OCR through Lucía, its AI assistant. The expense data comes in from the export; you upload the PDFs afterwards and Lucía reads them.
How long does it take with 500 invoices?
It depends on the file size, but there's no sync to wait for: you upload the export and, before confirming, you see a preview with exactly what will be imported.
Can I also migrate recurring invoices and quotes from Quipu?
No. Recurring invoices and quotes aren't imported from the export: you set the recurring invoices up again in Cofactu, which has them too, and recreate any quotes that are still open.
What if Sage ends up shutting Quipu down?
All the more reason to get the export done sooner rather than later. Cofactu doesn't depend on Quipu post-import: your data lives in our database (Neon, EU) and you can export it to CSV/Excel/JSON whenever you want.
Start with a copy, not a surrender Bring a sample and check
Bring a sample and check
before you switch.
Create your account, import the first data from Quipu and check the result without cancelling your current tool yet.
