Migrate your invoicing.
Guides by program.
A migration starts by knowing the source, continues with a review and ends when you know which history stays available to work with. Cofactu's guides put that path in order, program by program.
One rule for the move: don't go ahead with an automatic import before checking what the export contains and how your historical documents will be treated.
See comparisons →
The migration passport:
source, scope, review, ready.
A manifest that only makes sense when moving a history between two systems, and that turns the guide into a series of explicit checks.
Source identified You select the program and follow its export guide, without assuming every plan offers the same route.
Scope defined You decide which clients, products and historical documents should be part of the move.
Data checked You check columns, dates, series and possible duplicates before confirming the import.
New operations The history stays separate from new invoices and the team can carry on from Cofactu.
Migration workbench
| Stage | What it is | Item | Detail |
|---|---|---|---|
| 01 · Source export | What comes out | clientes.xlsx | People and tax details |
| 01 · Source export | What comes out | productos.csv | Catalogue and VAT rates |
| 01 · Source export | What comes out | facturas.csv | Historical documents |
| 02 · Control gate | What is decided | 01 | Columns recognised |
| 02 · Control gate | What is decided | 02 | Duplicates set aside |
| 02 · Control gate | What is decided | 03 | Series confirmed |
| 03 · Cofactu destination | What is ready | History kept separate | Available to consult without altering the new numbering. |
| 03 · Cofactu destination | What is ready | Review | Before importing |
The workbench shows the prior check; it does not assume every vendor exports the same files.
Nine starting points.
A review before you move.
Each program keeps its own route because the exports and permissions available can vary by product, plan or version.
- 01 Holded API + CSV · Migrate from Holded. The guide covers the API scope, issued invoices that arrive as historical records and checking the source documents.
- 02 Quipu Excel · Migrate from Quipu. The guide starts from the Quipu Excel export, available on all its plans, which Cofactu recognises.
- 03 Billin CSV / XLSX · Migrate from Billin. The guide starts from the Billin CSV/Excel export, available on all its plans, which Cofactu recognises.
- 04 Anfix Excel · Migrate from Anfix. The guide starts from the export from reports; Cofactu suggests which field each column maps to.
- 05 Sage 50 CSV / XLSX · Migrate from Sage 50. The guide starts from the export from the invoicing module.
- 06 Factusol Excel + Contasol · Migrate from Factusol. The route covers invoices, clients and products, plus Contasol accounting when it is used.
- 07 Contasimple CSV / Excel · Migrate from Contasimple. The guide starts from the exportable invoice lists.
- 08 FacturaDirecta CSV / Excel · Migrate from FacturaDirecta. The guide starts from the list export and suggests checking the mapping before continuing.
- 09 AEAT free app No export · Migrate from AEAT free app. The guide explains how to continue your numbering when the history cannot be exported to another system.
The check is not an extra step.
It is the migration done right.
The source files describe the past of your business. Reviewing them before importing saves you from deciding later on information already brought in.
| Source field | Destination | Check |
|---|---|---|
| Legal name | Client · Company name | Recognised |
| NIF / CIF (Spanish tax ID) | Client · Identifier | Exact check |
| Series / number | Historical document | Decide first |
| Date / total | Invoice · date / amount | Sampling |
Historical invoices and new invoices stay separate: how they are treated is confirmed before you start invoicing from Cofactu.
Start with the export.
Then we decide the route.
If your program doesn't have a published guide yet, tell us which export format it offers and what you need to move. We will review the route with you before assuming compatibility.
Frequently asked questions
Which programs can I migrate to Cofactu from?
There are guides for migrating from 9 programs: Holded, Quipu, Billin, Anfix, Sage 50, Factusol, Contasimple, FacturaDirecta and the AEAT free app. Each one explains that program's route (API, CSV or Excel), because the export changes by product and plan. If yours is not listed, write to hola@cofactu.com with the export format it offers.
Which file formats does Cofactu import?
CSV and Excel (.xlsx and .xls) in all its importers, plus Norma 43 (the Spanish bank statement format) for bank statements. It recognises as-is the invoice export of Holded, Quipu, Sage, ContaPlus, Contasol and Billin, the expense export of Holded and the client export of Sage 50. With any other Excel file, Lucía, Cofactu's AI, suggests which field each column maps to and you review it before importing.
How do I switch from Holded to Cofactu without losing data?
By connecting Holded through its API: you generate an API key in Holded, paste it into Cofactu and contacts, products, invoices with their PDFs, purchases, quotes, collections and payments are imported. If you prefer not to use the API, you can upload the Holded export as CSV or Excel. It is best done between periods, at the end of a month or quarter, keeping the originals separately. Guide: migrating from Holded.
Are imported invoices sent to the AEAT again?
No. Invoices you import from the export of your previous program arrive as historical records: they count in your books, but they are not resent to the AEAT (the Spanish Tax Agency) and carry no QR code, because the source program already issued them. Invoices you issue from Cofactu from then on do follow the VeriFactu flow.
Can I migrate if I use the AEAT free app?
Yes, but without bringing the history: the app does not let you export the records to continue in another program. Your invoices remain available at the AEAT; in Cofactu you start the history from zero or enter it by hand. The guide explains how to continue your numbering.
