Take an estate of 300 regular forms. At 3 to 4 days of drafting each, that is 900 to 1,200 days before testing and driver work. Most leaders never run that sum until the migration budget is already approved. By then, the gap between the plan and the real effort is hard to close.
This post gives you a way to size your own estate. It uses measured per-form drafting times and states what those times leave out. It also shows you how to run the numbers with your own count. A good SAP Service Provider will walk you through the same exercise before quoting a single day.
How much effort does one form really take?
A regular SAP form takes about 3 to 4 days of drafting effort to rebuild in Adobe Forms. That figure covers layout design, data binding, and scripting for one form. It excludes testing, output driver work, and rework after business review.
Those numbers come from measured per-form drafting work, and they are the starting point for any estimate. Three to four days sounds small. Multiplied across an estate, it becomes a program.
Here is the basic formula:
- Count the forms you actually use in production.
- Multiply by 3 to 4 days of drafting.
- Add testing and driver work as separate lines.
- Add a buffer for complex forms that break the average.
Run it for 300 forms and you get 900 to 1,200 days. Run it for 80 forms and you get 240 to 320 days. The method stays the same, so you can size any estate in a few minutes.
Why the drafting figure is only one line
Drafting is the visible part of the work. A developer opens the old Smartform or SAPscript, studies the layout, and rebuilds it in Adobe LiveCycle Designer. That is the 3 to 4 days.
Everything around it sits outside the figure. A tester must check the output against real data. A developer must adjust the print program or output driver. The business team that owns the document must give sign-off. Each of those steps adds time, and none of it appears in the drafting number.
What a regular form looks like
A regular form is not a one-page label, and it is not a multi-section customs pack. Think of a standard sales invoice or a delivery note. It has a header, an item table, totals, and a footer with legal text. It pulls data from one main structure and a few lookups.
Forms like this follow predictable patterns. A developer who has built ten of them knows where the traps sit. That is why the 3 to 4 day figure holds up on regular documents but breaks on unusual ones.
What does the drafting estimate leave out?
The drafting estimate leaves out testing, output driver work, form-specific scripting surprises, and business approval cycles. These items often match or exceed drafting time on complex documents. A reliable plan lists each as its own line rather than hiding them in a single contingency percentage.
Here is what sits outside the 3 to 4 days:
- Unit and integration testing against real transaction data.
- Output driver and print program changes.
- Output device and printer testing across plants.
- Business review rounds and layout corrections.
- Language and country variants of the same form.
- Archiving, email, and fax output checks.
Each item scales differently. Testing scales with form count. Driver work scales with the number of distinct print programs, which is often lower than the form count. Variants scale with your footprint across countries.
The variant trap
A single invoice can exist in six languages and four country layouts. Teams sometimes count that as one form. Others count it as twenty-four. Neither answer is wrong, but you must decide before you estimate. Otherwise the numbers swing by an order of magnitude.
A practical rule: count each distinct layout as a form, and treat pure language changes as a small add-on. That keeps the estimate honest without inflating it.
Where testing time really goes
Testing looks cheap on a spreadsheet and expensive in practice. A tester needs real documents, not dummy data. Finance wants to see an invoice with credit memos, partial deliveries, and tax splits. Each scenario needs a posted transaction behind it.
Setting up that data often takes longer than checking the output. So teams that plan test data early save days later. Teams that wait until the form is built usually stall for a week while someone creates the right orders.
How do you run the numbers on your own estate?
You run the numbers by sorting your forms into simple, regular, and complex groups, then applying a different time to each group. Regular forms use the 3 to 4 day figure. Simple forms take less. Complex forms take more. Add separate lines for testing and drivers.
Start with an inventory. Pull your output types, check which forms actually print, and remove dead ones. Many estates carry forms nobody has sent in years. Retiring them is the cheapest saving in the whole program. The SAP Community migration walkthrough offers a useful technical view of how Smart Forms map across to Adobe Forms.
Then follow this process:
- Export the list of forms from your system, including Smartforms, SAPscript layouts, and custom Z forms.
- Check output history to see which forms printed in the last twelve months.
- Group the survivors into simple, regular, and complex.
- Apply a drafting time to each group, using 3 to 4 days for regular.
- Add testing, driver work, and variant lines separately.
- Add a buffer based on how many complex forms you found.
A worked example
Say your inventory shows 400 forms. Output history shows 120 never printed in the past year, so you retire them. That leaves 280. Of those, 60 are simple, 180 are regular, and 40 are complex.
Regular forms alone come to 540 to 720 days at 3 to 4 days each. Simple forms might take 1 to 2 days each, so 60 to 120 days. Complex forms might take 8 to 10 days each, so 320 to 400 days. Your drafting total lands between 920 and 1,240 days, and you have not yet counted testing.
Notice what happened. The original count of 400 would have suggested 1,200 to 1,600 days on the regular rate alone. Cleaning the list first changed the shape of the plan. That is why inventory comes before estimation.
How to size complex forms
Complex forms deserve their own estimate, because the average hides them. A customs declaration, a multi-page contract, or a dynamic statement with conditional sections can take two or three times the regular figure. Pick five or six of them and have a developer rebuild one as a trial. The result gives you a real number instead of a guess.
Which factors push the effort up or down?
Form complexity, team experience, reusable components, and sign-off speed move the per-form effort most. A team with a shared template library can beat the 3 to 4 day average. A team starting cold, with slow approvals, will exceed it.
Think of these as dials rather than fixed costs:
- Reuse: a shared header, footer, and address block cut repeat work on every form.
- Experience: developers who know the tool avoid common binding mistakes.
- Data model: clean, well-documented structures speed up data binding.
- Governance: fast business sign-off removes idle days between rounds.
- Tooling: a standard naming convention and version control reduce rework.
Reuse deserves extra attention. If 200 forms share the same company header, build it once as a fragment. Every form after that inherits it. Teams that skip this step rebuild the same block hundreds of times and pay for it in both drafting and testing.
Why team makeup matters
A single expert can draft quickly but becomes a bottleneck. A larger team drafts in parallel but needs shared standards. The right mix depends on your deadline and your estate size. For a few dozen forms, one or two developers are enough. For several hundred, you need a small squad with a lead who owns the templates.
This is also where outside help earns its keep. A SAP Service Provider that has already built a template library can start at the fast end of the range from week one. Your internal team, learning as it goes, usually starts at the slow end.
How should you plan the program around the numbers?
Plan the program in waves, starting with high-volume, low-risk forms and ending with the complex ones. This order builds team speed early, exposes driver issues sooner, and keeps business reviewers engaged without overloading them in any single sprint.
A wave plan might look like this:
- First: ten to twenty regular forms, such as invoices and delivery notes, to prove the template library and test process.
- Second: the bulk of regular forms, built in parallel with a shared standard.
- Third: country and language variants, using the templates from earlier stages.
- Last: complex forms, each with its own estimate and owner.
Each stage ends with a measurement. Compare actual drafting days to your 3 to 4 day assumption. If the first stage runs at five days per form, you learn that before you commit the whole budget. If it runs at two, you can bring the end date forward.
What happens after go-live
Forms do not stop needing attention once they print correctly. Tax rules change, legal text updates, and business units ask for layout tweaks. Plan for that tail. Good SAP Support Services cover form changes, output troubleshooting, and fixes after upgrades, so your team does not carry every small request alone.
Without that cover, minor requests pile up in the development queue. Within a year, the new forms start to drift from the standards you built. A light support arrangement costs far less than a second cleanup program.
What mistakes inflate form migration budgets?
The most common budget mistakes are counting dead forms, ignoring variants, skipping complex-form trials, and treating testing as an afterthought. Each one is avoidable, and each one shows up in the plan long before the first form gets built.
Watch for these patterns:
- Quoting from the full inventory without checking output history.
- Using one flat rate for every form regardless of complexity.
- Leaving testing and driver work inside a vague contingency line.
- Starting without a shared template library.
- Waiting for business sign-off until the end instead of each stage.
Moving to a modern ERP platform raises the stakes on these choices. If you run the numbers alongside your wider SAP S/4HANA plan, forms become one workstream with its own owner and its own milestones. Treat them as a side task and they will surface as a late surprise.
A short checklist before you approve the budget
Before you sign off, ask your team five questions. How many forms did you count, and how many printed in the last year? How did you treat variants? Which complex forms did you trial? Where do testing and driver days appear in the plan? Who signs off each stage, and how fast?
If any answer is vague, the estimate is not ready. Sending it back costs a day. Approving it as is can cost months.
Turning per-form math into a budget you can defend
The per-form figure of 3 to 4 days gives you a fair starting point, but it only covers drafting. A defensible budget adds testing, driver work, variants, and a buffer for complex documents, each on its own line. It also starts from a cleaned inventory, not the raw list.
Once you have those lines, you can show finance exactly where each day goes. You can also adjust the plan when the first stage produces real data. That beats a single contingency percentage that nobody can explain.
Frequently Asked Questions
Q. How many days does it take to convert one SAP form to Adobe Forms?
A. A regular form takes about 3 to 4 days of drafting effort. That excludes testing, output driver work, and business review rounds. Simple forms take less and complex forms take considerably more.
Q. Should I migrate every form in my SAP system?
A. No. Check output history first and retire forms that have not printed in the last year. Cleaning the inventory is the cheapest way to cut effort in the whole program.
Q. How do I count forms that exist in many languages?
A. Count each distinct layout as one form and treat pure language changes as a small add-on. Decide the rule before you estimate so your numbers stay consistent.
Q. Can a template library reduce the 3 to 4 day average?
A. Yes. Shared headers, footers, and address blocks cut repeat work across forms. Teams with a mature library often beat the average, while teams starting cold tend to exceed it.
Q. Who supports forms after go-live?
A. Your internal team can, but many companies hand form changes and output fixes to a partner. 2iSolutions offers support arrangements that cover layout updates, output troubleshooting, and post-upgrade fixes.
See where these numbers come from: register for December 2: Link
Want this applied to your SAP estate?
Tell us where you are and we'll come back with a concrete next step.
Talk to our team