Official guide · 5 min

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 in under 5 minutes via Quipu's official API (Pro plan) or by uploading the Excel export. Invoices already sent to AEAT keep their original CSV; new ones start the VeriFactu hash chain from scratch.

No card required · Free plan forever · Migration at no cost

During the migration

Migrate with peace of mind — nothing gets lost along the way

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.

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.

No lock-in

If you ever wanted to go back, you export ALL your Cofactu data in 1 click (clients, invoices, expenses, PDF + signed XML). We don't block the exit — transparency runs both ways.

Step by step

Two ways to bring in your data

Automatic API sync (the fast option) or uploading your Excel/CSV export. Both cover clients, products, and invoices from Quipu.

Recommended

Option A · Quipu API

1

Get your Quipu API key

~ 30s

Go to Quipu → Settings → API → Generate new key. Requires a Pro plan or higher.

If you're on the Basic plan (€12), the API isn't available — use option B (Excel export) instead. Cofactu only needs read permissions. The key is encrypted with AES-256-GCM on our server and never logged.

2

Paste it into Cofactu Settings → Integrations

~ 1 min

Create your free Cofactu account and paste the API key into Integrations → Quipu.

If you don't have an account yet, the signup wizard takes you straight to the integration step after the verification email.

3

Import with one click

~ 2-3 min

Cofactu brings in your clients, products, and historical invoices as reviewable drafts.

Invoices arrive in draft status — you review them before resubmitting to AEAT. Ones you already sent from Quipu are NOT resubmitted; they keep their original CSV with an 'Accepted by AEAT (imported)' badge.

Alternative

Option B · Excel/CSV export

1

Export from Quipu

~ 1 min

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.

2

Upload the files to Cofactu

~ 1 min

Create your free account and go to Invoices → Import → From another program → select Quipu.

The parser detects the Quipu format automatically. If your export has custom columns (tags, extra fields), you get an editable preview before committing to map them to Cofactu fields.

3

Confirm and go

~ 2 min

Review the preview with N invoices + M clients and hit Import. Done.

Same as with the API: historical invoices keep their Quipu numbering (e.g. F-2025-0142) and come in as drafts. If they already have an AEAT CSV, they're imported as accepted.

After migrating

What you get in Cofactu that you didn't have in Quipu

Before · Quipu
  • Real VeriFactu from day 1
  • PSD2 bank connection included
  • Human support with no premium gating
  • AEAT filings submitted directly
Now · Cofactu
  • 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.

  • PSD2 bank connection included

    Over 40 Spanish banks via Enable Banking (EU-regulated AISP). Sync every 6h, auto-reconciliation with invoices, and T-7/T-3 alerts before authorization expires. In Quipu, banking is a separate module billed extra.

  • Human support with no premium gating

    Human chat on every Cofactu plan (including the free one). Quipu reserves phone support for the €49/month Premium plan — and standard chat is slower on lower-tier plans.

  • AEAT filings submitted directly

    Cofactu files 303/111/130/115 + 190/347/349 with AEAT straight from the app and returns the official CSV. Quipu only generates the file for you to upload yourself to the tax portal — and filings are restricted to the €36/month Business plan.

Clean chain

Your VeriFactu hash chain starts clean with your first new invoice

Invoices you already sent to the AEAT from Quipu keep their CSV — we don't touch them. From your first invoice in Cofactu, the SHA-256 hash chain links up whole, signed, and verifiable, with no baggage from the past.

  • Quipu history imported and searchable
  • New chain linked and signed from day 1
  • Automatic repair if an invoice breaks the chain (error 4171)
Once you've migrated

File your AEAT tax forms directly from Cofactu

Where Quipu makes you download the file and upload it manually to the AEAT portal, Cofactu files it directly. Covers all 7 forms with the official CSV saved in an immutable audit log.

FAQ

Preguntas frecuentes

The most common questions when migrating from Quipu to Cofactu.

¿No encuentras tu respuesta?

Escríbenos y te contestamos en menos de 24 h hábiles. Gente real, no tickets.

hola@cofactu.com Talk to support
Are my invoices already sent to AEAT from Quipu resubmitted?
No. Cofactu detects the ones that already have an AEAT CSV and marks them 'accepted (imported)' — they're not resubmitted, no duplicates. 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. The API requires a Pro plan or higher; the Excel export is available on every plan (including the €12 Basic). If you don't have a Pro plan, go straight to Option B with the Excel file.
What happens to my OCR expenses from Quipu?
Cofactu has its own OCR through Lucía, its AI assistant. Imported expenses arrive with their attached PDFs when they come via API; with CSV, the structured data is imported and you upload the PDFs afterward in bulk.
How long does it take with 500 invoices?
API: 3-5 minutes (paginated sync, without touching AEAT). CSV: 2 minutes of upload + parse + commit. The preview is shown before the commit so you see exactly what will be imported.
Can I also migrate recurring invoices and quotes from Quipu?
Yes. Quipu's recurring invoices are imported as Cofactu templates (same client, same amount, same cadence). Quotes arrive as quote drafts, not invoices — you convert them with one click once they're approved.
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.

Shall we get started?

Create your free account and start migrating from Quipu in under 5 minutes. If you get stuck at any step, we'll help you over chat.