Contract migration for CLM roll-outs and carve-outs: effort and roles

Short answer: The effort of a contract migration project depends on contract volume, review depth and the state of the repository. A CLM roll-out captures legacy contracts with metadata; a carve-out also allocates and transfers them. You need a lead, project lawyers or contract managers for review, and junior profiles for data capture. In our experience, CLM projects take 3–9+ months.

This guide is for general counsel, heads of legal and legal operations leads in Switzerland and Germany. It shows how to estimate the effort of a contract migration project, which roles to staff and where a CLM roll-out differs from a carve-out.

What contract migration means in CLM roll-outs and carve-outs

Contract migration means finding existing contracts, reviewing them and moving them into a new target state. In a CLM (contract lifecycle management) roll-out, the target is a contract management system with reliable data. In a carve-out, the target is a separated business that starts with the right contracts.

Both projects share the same core: build a contract inventory, review it against a checklist and document the result. They often coincide, for example when the separated business starts with its own CLM system. The guide Legal operations in a CLM implementation covers the full CLM project plan; Legal capacity for carve-outs covers all carve-out workstreams.

Estimating effort: the drivers

Volume, review depth and the state of the repository drive the effort, not the software. Measure these three early and your capacity plan will be realistic.

• Volume: the number of active contracts, including amendments and schedules. Migrate expired contracts only if they still trigger obligations.
• Review depth: capturing metadata is faster than reviewing assignability or change of control. Define contract classes, such as standard contracts, negotiated contracts and framework agreements with call-offs.
• State of the repository: scattered storage, paper files, missing signed versions and several languages add significant effort.
• Decision paths: who decides unclear cases, and how quickly? Missing escalation rules slow down every project.
• Tools: automated extraction speeds up data capture, but it does not replace legal review of fields with legal consequences.

How to calculate (worked example): run a pilot on a sample per contract class and measure the average review time. Multiply it by the number of contracts in each class and add a margin for quality control and clarifications. Divide the result by the productive hours per full-time person. With a 42-hour week, 46 working weeks and 70 % productive time, that is around 1,350 hours a year, or around 29 hours a week. This tells you how many people you need for the planned timeframe.

Step-by-step approach

A contract migration works when the data model and decision rules are fixed before bulk review starts. This sequence has proven itself:

1. Define scope: which entities, contract types and periods are in? For a carve-out: which contracts relate to the separated business?
2. Define data model and checklist: mandatory fields, review questions and permitted values, including rules for shared contracts.
3. Collect the population: bring together contracts from legal, procurement, sales and business units and remove duplicates.
4. Pilot: review a sample per contract class, measure review time, sharpen the checklist.
5. Bulk review: allocate contracts by class and escalate unclear cases to the lead.
6. Quality control: sampling, with closer checks on fields with legal consequences such as notice periods.
7. Implementation: for CLM, import and acceptance; for a carve-out, consent letters, transfer agreements and follow-up.
8. Handover: pass open points, decisions and data rules to the business-as-usual team.

Roles and capacity

A contract migration needs a small core team with a clear split: one lead who decides and several people who review and capture. The table shows a typical set-up; size and workload depend on the measured volume.

The in-house legal team keeps control and makes the decisions with legal consequences. For splitting large review volumes across a team, see Clearing a contract review backlog. For the profiles that suit the review work, see Interim contract managers: tasks, profile and engagement models.

Alpinum Solutions provides leads, project lawyers, contract managers and junior profiles through staff leasing or freelancing, part-time or full-time at a workload of 20–100 %, as individuals or as a team. Selected profiles are usually available within 48 hours; companies and Alpinum agree the start date together. As a reference: in an international carve-out, Alpinum Solutions supported an industrial company with experienced interim legal specialists for the legal separation of several entities, the review and transfer of existing contracts, and the coordination of corporate and regulatory requirements across several jurisdictions.

Switzerland and Germany: what differs

The method is the same in both countries. Differences lie in the law governing the contracts and in the framework of the engagement model.

In Austria, assignments run as freelancing or as staff leasing through the German or the Swiss entity.

Limits and risks

• Legal assessment stays in-house: whether a contract can be transferred and which consents are needed is assessed by the legal team and its external counsel. Alpinum is not a law firm and does not give legal advice.
• Underestimated volume: without a pilot, review time is almost always set too low. Plan capacity per phase and adjust it after the pilot.
• Data quality: errors in notice periods or renewals only show months later. Apply closer quality control to these fields.
• Confidentiality: the team sees prices, terms and deal details. Access rights and confidentiality rules belong before the start.
• Knowledge loss at the end: without a handover, decisions and data rules get lost. Plan the handover as a separate step.

Frequently asked questions about contract migration projects

How long does contract migration take in a CLM roll-out?

Based on Alpinum's assignment experience, a CLM implementation typically takes 3 to 9 months, sometimes longer depending on scope. Contract migration is usually the most time-consuming part. Its duration depends on the number of contracts, the review depth and the state of the repository. A pilot on a sample per contract class gives you the figures for a reliable plan.

Which contracts should be migrated?

Focus on active contracts with running obligations, deadlines or renewals, including amendments and schedules. Expired contracts are only worth migrating if warranty, confidentiality or retention obligations still apply. A clear scope decision at the start often saves more time than any tool. Record the decision in the project charter.

How does a carve-out differ from a CLM roll-out?

In a carve-out, capturing data is not enough. Each contract has to be allocated to the separated business or the group, reviewed for assignability, consent requirements and change-of-control clauses, and then transferred, split, re-papered or terminated. The deal timetable with signing and Day 1 also sets fixed dates that are hard to move.

Does automated extraction replace legal review?

No. Tools speed up capturing counterparties, dates and standard clauses. Fields with legal consequences, such as notice periods, liability caps or change of control, still need legal review, at least on a sample basis. Decide upfront which error rate is acceptable per field and who decides unclear cases.

Which profiles does a migration team need?

A typical team has a senior lead who owns the checklist and decisions, experienced project lawyers or contract managers for review, and junior profiles for data capture. Legal operations configures the data model in the system. All profiles are available through staff leasing or freelancing, part-time or full-time.

Next step

Alpinum Solutions is the leading provider of interim legal & compliance in the DACH region. Tell us the volume, timeline and roles you need, and you will receive selected profiles for staff leasing or freelancing.

• Legal & compliance transformation: project lawyers for CLM roll-outs and migration
• Legal operations in a CLM implementation: data, clauses and roll-out
• Legal capacity for carve-outs: workstreams, roles and timeline
• Roles & practice areas: all guides on roles and practice areas
• Discuss your needs

Last updated: 11 November 2026.