Compare
What moving from innoscripta to Grants actually looks like in 2026.

Grants is what people use when innoscripta stops fitting. Below is the honest side-by-side - same product surface, different posture: hosted in Germany, no third-party trackers, one honest price - plus the migration mechanics that decide whether the switch lands in an evening or in a quarter.
innoscripta is an excellent platform if you're an established R&D-active company with payroll for technical staff and a recurring Forschungszulage claim each year. They're a Munich-headquartered SaaS with 2,500+ paying customers and an IPO in 2025 - they earned that scale by being good at the job. The job, however, is administering an ongoing R&D operation for tax-credit compliance - time tracking, audit-ready documentation, capacity planning. Grants does a different job: it gets a startup from a draft Ideenpapier to a submitted EXIST, IGP, KMU innovativ, BMBF, or Horizon application. Where innoscripta plugs into an HR/payroll system, Grants plugs into a writing workflow. Pick by job.
Switching
The switch goes in three rough phases: export from innoscripta, import into Grants, and reorganise what came over. Most people allocate an evening for it. The export side is where the time goes - innoscripta hands you a CSV/JSON dump and the field mapping isn't always obvious; once that's resolved the import is a couple of minutes. We don't paywall the import path or pretend it's a pro-only feature, and you can run both side-by-side while you decide.
Find the export option in innoscripta's account settings. Most tools provide a CSV or JSON download. Save the dump locally - that's the source of truth for the next step.
Open the import tool in Grants. innoscripta's field names rarely match Grants' 1:1; the import flags any unmapped columns so you can pair them up before anything commits.
Run the import. Grants shows a preview of the first parsed rows in the import dialog so you can sanity-check the column mapping + a sample of records before anything commits. If you're nervous about a large dump, import a small subset first, verify it landed the way you expected, then run the full file.
innoscripta-specific UI metadata (custom views, saved filters, in-app annotations) doesn't transfer with the data export. Spend an evening rebuilding the views you used most - usually a 30-minute job once you've done it once.
Run both side-by-side for a couple of weeks if you want to be sure. When you're confident, cancel the innoscripta subscription from their side. Grants keeps your export option self-serve in account settings - no lock-in either direction.
Switching from innoscripta
Free plan, no credit card. We host in Germany. Export + delete are self-serve.
Read next
Full Grants vs innoscripta
When the established-R&D-team platform isn't the right tool for a founding team.
Read
Forschungszulage: Germany's R&D tax credit, expanded by the Wachstumschancengesetz
What counts as R&D, how BSFZ certification works, and how to stack with grants.
Read
Grants vs Microsoft Word for EXIST applications
Where Word still wins, and where it costs you the grant.
Read
Grants vs Google Docs for grant applications
Honest comparison - co-editing wins, structure does not.
Read
| Ours Grants | Theirs innoscripta | |
|---|---|---|
EXIST / Forschungstransfer / IGP / BMBF / EU grant writing | ||
Forschungszulage time-tracking + audit-ready compliance | ||
BSFZ certification workflow | ||
Section-structured grant editor (Ideenpapier chapters) | ||
PTJ / reviewer-language coaching inside the editor | ||
HR / payroll-system integration for ongoing R&D ops | ||
Startup-stage pricing | Enterprise tier | |
Hosted in Germany |