Transfer a bike fit between bikes: read the complete measurement record
Before copying a position to a second bicycle, distinguish comparable contact measurements, component context and unresolved references. Read fifteen fictional fields and two withheld-comparison cases without creating profiles.
Published 26 October 2026 · OpenBikeFit
A reference gate, not a fit score
- Fictional source
- 550 mm
- Fictional target
- 558 mm
Same named points, method and required confirmation?
Declared in packet A → +8 mm
Target minus source. A numerical difference, not work to perform.
Different or unconfirmed → withheld
Identical visible values do not supply the missing reference evidence.
On this page
- 01Name the two records before comparing
- 02Keep the shared reference bundle visible
- 03Read all fifteen declared fields
- 04Read a difference without turning it into work
- 05Keep eight context fields out of the action queue
- 06Withhold unlike endpoints and missing values
- 07Keep unconfirmed references separate from matching values
- 08Do not use one matched coordinate as a matched bicycle
- 09Keep crank length and contact hardware as questions
- 10Freeze a baseline before a deliberate plan
- 11Read installation and remeasurement as separate records
- 12Choose paper, reading or the local workflow deliberately
Keep the next record separate
Read the blank measurement worksheet
An empty paper preview, not a prefilled bicycle, a transfer plan or a file action.
Open toolCan you transfer a bike fit to another bike? You can compare recorded observations when their definitions genuinely match. That is a narrower task than establishing a suitable riding position, reproducing the feel of a different bicycle or deciding that a component can be installed. Start with a named source record and an independently recorded target baseline. Keep the missing facts visible instead of letting familiar numbers fill the gaps.
This is a public reading guide, not a fitting or assembly procedure. The three packets below are deliberately fictional declarations passed through the existing OpenBikeFit comparison. They create no bicycle profiles, transfer plan, installation record or rider result. Use them to understand what a comparison says before deciding whether to enter your own information. The source could be a second road bike, an indoor bicycle or a rental record; that label alone establishes neither equivalent measurement points nor an appropriate use.
Name the two records before comparing
Write which bicycle and which recorded occasion each set of values describes. Source means the record you are considering as a reference, not the better bicycle or a clinically validated position. Target means the separately described bicycle being compared, not a collection of automatically approved settings. Preserve its original observations even if you later make a deliberate plan. Without that baseline, a return to an earlier state becomes another assumption rather than a documented comparison.
Keep the measuring occasion separate from a component catalogue. A printed frame chart, a stem marking, a saved observation and a proposed value can all use millimetres, but they describe different evidence. Record whether an entry was actually observed, copied from a named specification or left unresolved. Do not replace a target observation with the source simply because the source record is more complete. A complete-looking sheet assembled from both bicycles is not an independent baseline for either.
Keep the shared reference bundle visible
Name the origin, endpoint, direction and method before reading a difference. In the fictional packet, saddle height ends at a marked top-surface station and setback follows its stated horizontal convention. Cockpit reach and drop refer to the named saddle and right-hood points with horizontal and vertical methods. Saddle tilt uses a named bridge line; hood angle and hood height have their own surface and datum. These written declarations are part of the example, not evidence that a person physically followed them.
The external sources below illustrate why names matter. Foundation describes its own saddle station and distinguishes primary contact coordinates from secondary component information. Simplon names the grip-position quantities used by its particular converter. Velogic defines separate bar, hood and frame coordinates. Their labels are not a universal shared dictionary. Read the exact definition in the actual report; do not silently translate a bar-clamp point into a hood trough or a direct tape length into a horizontal separation.
- 1 · Name the datum. Keep BB origin, the saddle point, the control point and each direction.
- 2 · Read two records. Source and target were declared independently; neither is automatically ideal.
- 3 · Check the reference gate. A missing value, different bundle or absent confirmation withholds the affected difference.
- 4 · Keep the next task separate. A numerical comparison is not mechanical work, an installed observation or a fit verdict.
Read all fifteen declared fields
Packet A shows every field used by the existing complete-setup comparison, not only the numbers convenient to copy. The source and target have coherent written references and explicitly fictional confirmations. Seven rows describe contact quantities; eight retain component or frame context. All fifteen numerical source and target declarations stay visible beside their units and the returned difference. The two zero differences are actual zeros in this fictional arithmetic, not replacements for missing information.
Read the role label before the value. A comparable declaration means the software has enough stated information to subtract these entries under its rules. Numerically equal means that subtraction is zero. Neither says that an instrument was accurate, the bicycle was level, the source is suitable or the target is physically attainable. The whole packet remains an educational example even where the app returns a technically available difference. A caption or badge must not promote that arithmetic into an installation decision.
Static reading example · not your bicycles
A · Complete fictional source and target
All fifteen fields are shown. Seven contact fields and eight component/frame fields have different roles; a difference is arithmetic, not an instruction.
Saddle height
Contact field · Comparable declarations
- Source A
- 742 mm
- Target declaration
- 738 mm
- Target minus source
- -4 mm
No mechanical action, installed setting or suitable rider position follows from this number.
Saddle setback
Contact field · Comparable declarations
- Source A
- 62 mm
- Target declaration
- 65 mm
- Target minus source
- +3 mm
No mechanical action, installed setting or suitable rider position follows from this number.
Cockpit reach
Contact field · Comparable declarations
- Source A
- 550 mm
- Target declaration
- 558 mm
- Target minus source
- +8 mm
No mechanical action, installed setting or suitable rider position follows from this number.
Cockpit drop
Contact field · Comparable declarations
- Source A
- 80 mm
- Target declaration
- 75 mm
- Target minus source
- -5 mm
No mechanical action, installed setting or suitable rider position follows from this number.
Saddle tilt
Contact field · Numerically equal
- Source A
- 1.5 °
- Target declaration
- 1.5 °
- Target minus source
- 0 °
No mechanical action, installed setting or suitable rider position follows from this number.
Hood angle
Contact field · Comparable declarations
- Source A
- -2 °
- Target declaration
- 0 °
- Target minus source
- +2 °
No mechanical action, installed setting or suitable rider position follows from this number.
Hood height
Contact field · Comparable declarations
- Source A
- 12 mm
- Target declaration
- 8 mm
- Target minus source
- -4 mm
No mechanical action, installed setting or suitable rider position follows from this number.
Crank length
Context only — not a transfer step · Comparable declarations
- Source A
- 170 mm
- Target declaration
- 172.5 mm
- Target minus source
- +2.5 mm
Different frame or component declarations are context, not a request to change them.
Head angle
Context only — not a transfer step · Comparable declarations
- Source A
- 73 °
- Target declaration
- 72.5 °
- Target minus source
- -0.5 °
Different frame or component declarations are context, not a request to change them.
Spacer height
Context only — not a transfer step · Comparable declarations
- Source A
- 20 mm
- Target declaration
- 10 mm
- Target minus source
- -10 mm
Different frame or component declarations are context, not a request to change them.
Bar width
Context only — not a transfer step · Comparable declarations
- Source A
- 400 mm
- Target declaration
- 420 mm
- Target minus source
- +20 mm
Different frame or component declarations are context, not a request to change them.
Stem length
Context only — not a transfer step · Comparable declarations
- Source A
- 100 mm
- Target declaration
- 110 mm
- Target minus source
- +10 mm
Different frame or component declarations are context, not a request to change them.
Stem angle
Context only — not a transfer step · Numerically equal
- Source A
- -6 °
- Target declaration
- -6 °
- Target minus source
- 0 °
Different frame or component declarations are context, not a request to change them.
Frame stack
Context only — not a transfer step · Comparable declarations
- Source A
- 575 mm
- Target declaration
- 590 mm
- Target minus source
- +15 mm
Different frame or component declarations are context, not a request to change them.
Frame reach
Context only — not a transfer step · Comparable declarations
- Source A
- 390 mm
- Target declaration
- 395 mm
- Target minus source
- +5 mm
Different frame or component declarations are context, not a request to change them.
Read a difference without turning it into work
Target minus source is the target declaration less the source declaration. In A, cockpit reach is 558 minus 550, giving positive 8 mm. The opposite subtraction is negative 8 mm. Saddle height is 738 minus 742, giving negative 4 mm. Those signs tell you which listed value is larger under the stated convention. They do not identify a bolt to loosen, a component to buy, an amount of rail movement or a route through a mechanical adjustment.
A coordinate can depend on several installed dimensions, and a single mechanical change can alter more than one coordinate. Moving along an angled axis is not generally the same as moving vertically or horizontally. Do not treat the opposite numerical difference as a physical procedure or assume all other values would remain fixed. Any actual proposal needs the exact bicycle, parts, instructions and observations required by the separate workflow. This guide intentionally does not render the engine’s generated adjustment instructions.
Keep eight context fields out of the action queue
Crank length, head angle, spacer height, bar width, stem length, stem angle, frame stack and frame reach are the eight context rows in this packet. They help explain why two bicycles with related contact numbers are still different assemblies. For example, A records different frame stack and reach without making either one a transferable target. A frame dimension is not a movable control, and a component difference does not establish that another part would be compatible.
The context rows retain arithmetic where the existing comparison permits it, including the equal stem-angle declarations. They are not silently discarded because they are not selectable contact steps. Nor do the seven contact rows become physical instructions simply because the application can offer them in a separate deliberate plan. Keep description, model, proposal, installed observation and later re-check as distinct records. A numerical context difference may be a useful question for a qualified mechanic or fitter, not an automatic shopping list.
Withhold unlike endpoints and missing values
Packet B retains the same numerical declarations except that target hood height is unrecorded and the target’s written cockpit endpoint is now the handlebar-clamp centre, not the source’s right hood trough. The target measurement-reference bundle and its structured cockpit datum name that changed point together. The existing comparator withholds four spatial differences when the required bundle differs. Its conservative bundle check also withholds saddle spatial rows; it does not claim that changing a bar label physically changed a saddle.
All seven contact rows remain visible in B. The hood-height row has a missing target value and no invented difference. Independently defined saddle tilt and hood angle retain the states their own reference checks support. The eight component and frame declarations remain those in A. This is not an instruction to relabel unlike observations until they pass. Resolve the real endpoint and obtain any missing observation through the appropriate measurement process; preserve the old record as the account of what was actually declared.
Static reading example · not your bicycles
B · Changed endpoint and unrecorded hood height
The target now names the handlebar-clamp centre instead of the right hood trough, and has no hood-height reading. All seven contact fields remain visible. The eight context declarations are unchanged from A and still comparable.
Saddle height
Contact field · Reference bundle differs
- Source A
- 742 mm
- Target declaration
- 738 mm
- Target minus source
- Withheld — not zero
The existing app checks the whole named reference bundle before returning this difference; no endpoint conversion is inferred.
Saddle setback
Contact field · Reference bundle differs
- Source A
- 62 mm
- Target declaration
- 65 mm
- Target minus source
- Withheld — not zero
The existing app checks the whole named reference bundle before returning this difference; no endpoint conversion is inferred.
Cockpit reach
Contact field · Reference bundle differs
- Source A
- 550 mm
- Target declaration
- 558 mm
- Target minus source
- Withheld — not zero
The existing app checks the whole named reference bundle before returning this difference; no endpoint conversion is inferred.
Cockpit drop
Contact field · Reference bundle differs
- Source A
- 80 mm
- Target declaration
- 75 mm
- Target minus source
- Withheld — not zero
The existing app checks the whole named reference bundle before returning this difference; no endpoint conversion is inferred.
Saddle tilt
Contact field · Numerically equal
- Source A
- 1.5 °
- Target declaration
- 1.5 °
- Target minus source
- 0 °
No mechanical action, installed setting or suitable rider position follows from this number.
Hood angle
Contact field · Comparable declarations
- Source A
- -2 °
- Target declaration
- 0 °
- Target minus source
- +2 °
No mechanical action, installed setting or suitable rider position follows from this number.
Hood height
Contact field · Missing observation
- Source A
- 12 mm
- Target declaration
- Not recorded
- Target minus source
- Withheld — not zero
A missing target value is not replaced by zero or by the source value.
Keep unconfirmed references separate from matching values
Packet C uses exactly the values and written definitions from A but supplies none of the required reference confirmations. One shared spatial confirmation and three detail confirmations cover the seven contact fields. The existing rules withhold those seven contact differences. Raw values remain readable, including the equal saddle-tilt numbers; equal values do not provide the absent confirmation. The eight context comparisons remain available because the contact attestations are not their input. A ready outer packet therefore does not mean every row can be used for a contact comparison.
A confirmation is a statement made in the workflow, not an instrument reading or independent audit. It cannot make inaccurate observations accurate. Conversely, the absence of a confirmation does not prove that the bicycles differ physically; it limits what this software is prepared to present. Keep that distinction when reading an older record, an imported file or a colleague’s report. Do not infer a missing statement from a familiar component photograph, a matching profile name or another successful task elsewhere in the application.
Static reading example · not your bicycles
C · Same values, no reference confirmation
The fifteen declarations are exactly those in A. No reference confirmation is supplied: one spatial confirmation and three detail confirmations cover these seven fields. Their raw values remain visible without a difference; the eight context comparisons remain available.
Saddle height
Contact field · Confirmation absent
- Source A
- 742 mm
- Target declaration
- 738 mm
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Saddle setback
Contact field · Confirmation absent
- Source A
- 62 mm
- Target declaration
- 65 mm
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Cockpit reach
Contact field · Confirmation absent
- Source A
- 550 mm
- Target declaration
- 558 mm
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Cockpit drop
Contact field · Confirmation absent
- Source A
- 80 mm
- Target declaration
- 75 mm
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Saddle tilt
Contact field · Confirmation absent
- Source A
- 1.5 °
- Target declaration
- 1.5 °
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Hood angle
Contact field · Confirmation absent
- Source A
- -2 °
- Target declaration
- 0 °
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Hood height
Contact field · Confirmation absent
- Source A
- 12 mm
- Target declaration
- 8 mm
- Target minus source
- Withheld — not zero
Matching written definitions do not supply the separate declared confirmation.
Do not use one matched coordinate as a matched bicycle
Two equal listed quantities leave other facts unresolved. Different saddle shapes, control shapes, widths, contact surfaces, crank lengths or shoe-and-pedal arrangements can change what the rider experiences even when one coordinate matches. Different bicycle geometry and use can also change handling or the task being performed. The software comparison is not an assessment that those contexts are equivalent. It does not choose which differences are acceptable for a particular rider or intended activity.
The example’s equal tilt and stem-angle numbers make this boundary visible without a made-up success score. The same stated angle can sit on different components, refer to different physical lines or coexist with different positions. Where a comparison is withheld, do not search for a different matching row to stand in for it. Where it is available, keep the complete record beside it. A precise-looking signed number is not stronger evidence than the named observations that produced it.
Keep crank length and contact hardware as questions
The fictional crank lengths are 170 and 172.5 mm. That difference is component context, not a reason to compensate the saddle automatically. A separate crank-geometry model can state conditional relationships, but this reading packet does not run that model or establish its physical assumptions. It also does not show shoe, pedal or cleat dimensions, loaded contact behaviour or an independent rider assessment. No single correction can be inferred to close all those missing observations.
Likewise, a different bar width or stem length is not permission to swap parts. Exact model compatibility, marked limits, routing, condition and installation requirements belong to the relevant manufacturer instructions and competent physical review. Use the specialised field guides to understand the terms, not as substitutes for those exact documents. A question such as which point does this reach value describe is useful before a transfer; a generic instruction to reproduce every number is not a verified answer.
Freeze a baseline before a deliberate plan
If you choose the separate local transfer tool, it requires two saved profiles and the existing access and reference checks. It does not load the fictional values from this article. The source record and original target baseline remain different from the intended target values. Current saved-source checks at deliberate write actions can withhold a change when a selected record is missing, changed or ambiguous. Those checks concern saved data, not a continuous inspection of a physical bicycle.
Keep the original measurement record and the proposed work together for review without overwriting the distinction between them. A printed or exported copy is a separate snapshot and does not update itself when a profile changes. Opening a fixed guide link is not saving a plan, accepting a procedure or sending a report. If a workflow pauses, read its stated recovery path and inspect the current sources instead of assuming a later successful action silently repaired an earlier copy.
Read installation and remeasurement as separate records
A plan is a description of intended work. A recorded installation statement is another declaration, and a later measurement is an observation under its own method. Neither should be inferred from a comparison badge. The existing staged transfer workflow keeps its mechanical review and repeated re-check requirements; this article changes none of them. Read any named product matching window as a software criterion, not a guarantee about instrument accuracy, physical safety, comfort or suitability.
Repeated readings can expose variation but do not remove a shared mistake in the point or method. Preserve the individual readings and their reference rather than rounding away disagreement to make a target appear met. A keep, revert or stop record belongs to its actual occasion and scope. It is not a universal approval of the source position or a claim about a rider’s health. Resolve missing evidence or obtain appropriate human review instead of treating no available comparison as no problem.
Choose paper, reading or the local workflow deliberately
For a non-personal discussion, start with the blank worksheet. Its preview has named empty fields rather than this guide’s fictional numbers, and reading it creates no bicycle profile. Keep any completed personal record in your own appropriate controlled workflow; do not place another person’s details in a public example or a general business inquiry. A browser download or print is a separate choice and not proof that a mechanic received or reviewed the information.
Use the related measurement and frame guides when an endpoint or coordinate remains unclear. Use the local transfer workspace only when you deliberately want its saved-profile workflow and can supply the required records. Existing consent and any previously saved device state still apply. All public tools remain free; separately agreed B2B work concerns software or workshop workflow, not an included personal fitting service. None of the links carries the example values, a profile identifier or a command to start a transfer.
Practical questions
Frequently asked questions
Can I copy my bike fit to a second bicycle?
Comparable recorded quantities can be read together when their endpoints, directions and required confirmations match. That does not prove the source is suitable, the target can reproduce it mechanically or the bicycles will feel the same.
Is frame stack and reach enough to reproduce my position?
No. Frame stack and reach describe named frame points. Installed saddle and control coordinates have other endpoints and depend on additional components and observations. They remain separate context in the worked packet.
Which direction is target minus source?
Subtract the source declaration from the target declaration: 558 minus 550 is positive 8 mm. The reverse subtraction is negative 8 mm. Neither subtraction is a mechanical adjustment procedure.
Why can the same number have no available difference?
A missing required confirmation or a different reference bundle can withhold a contact difference even when both visible numbers are equal. Numerical equality does not supply evidence about their physical endpoints.
Why does changing a cockpit endpoint withhold saddle differences here?
The existing comparator conservatively checks the complete saved measurement-reference bundle for those spatial fields. The example shows that software rule; it does not claim the saddle moved or that the individual physical lengths became unequal.
Can a missing target measurement be treated as zero?
No. Packet B leaves hood height unrecorded and its difference withheld. Zero is a real declared value elsewhere in the example and is not used as a fallback for missing information.
Should I compensate automatically for different cranks or saddles?
No compensation is inferred by this reader. Crank length is context, and different contact hardware leaves additional physical questions. Any model, proposed work and actual re-check remain separate tasks with their own requirements.
Does opening the example save or transfer anything?
No. It is a fixed public reading record. The separate local tool requires your own saved profiles and existing gates. Fixed links carry none of the fictional quantities or profile identifiers and start no transfer, camera, download or acceptance.