What actually changes when a business converts a contractor to an employee in Ontario? Conversion is not just administrative. It changes the legal framework entirely and does not automatically erase whatever risk built up during the earlier contractor period. This article explains what status changes when conversion happens, why accrued risk survives the switch, and why documentation needs a fresh look rather than a simple carryover.
Key Takeaways
- Conversion is not just administrative. It changes the legal framework governing the relationship entirely.
- The individual moves from an independent business relationship into an employment relationship.
- That shift brings statutory protections and obligations that did not previously apply.
- Conversion does not eliminate past risk from before the change took effect.
- If the individual was misclassified earlier, liability may still exist for that prior period.
- New agreements must reflect the employment relationship clearly, not just relabel the old one.
- Old contractor terms cannot simply be carried forward into a new employment agreement.
Status Changes: What Conversion Actually Triggers
The individual moves from an independent business relationship to an employment relationship the moment conversion takes effect.
This brings statutory protections and obligations that did not apply before. Under the Employment Standards Act, 2000, an employee becomes entitled to minimum standards. These cover vacation pay, public holiday pay, overtime, and notice of termination. None of these applied to the same person while they were classified as a contractor. On the obligation side, the business now needs to withhold and remit source deductions. This includes income tax, CPP contributions, and EI premiums. The CRA's payroll deductions guide sets out exactly how this works. The business also typically becomes responsible for WSIB coverage. This generally does not apply to independent contractors in the same way.
This is a genuine shift in legal framework, not a change in job title. A business treating conversion as a paperwork update risks missing obligations that now apply automatically. Those obligations do not wait for the business to catch up.
A business that misses this shift often discovers it the hard way. A missed CPP remittance deadline is one common trigger. A WSIB premium assessment arriving months later is another. The obligations attach from the effective date of conversion, not from whenever the paperwork actually gets filed. A gap can open between the practical date the relationship changed and the date the paperwork caught up. That gap itself creates a small window of exposure worth closing quickly.
Accrued Risk: Why the Past Does Not Disappear
Conversion does not eliminate past risk from the period before the change took effect.
The individual may have been misclassified during the contractor period. If so, liability may still exist for that prior period. This exposure sits entirely separate from the new employment relationship going forward. The CRA can reassess the earlier period if the classification was wrong from the start. It can demand unpaid source deductions, along with penalties and interest. This is not hypothetical. A business converting a role because it doubts the original classification is flagging the exact issue an auditor looks for.
The connection to the CRA's test for contractors in Ontario is direct here. Control, tool ownership, financial risk, and integration might all have pointed toward employment during the contractor period. If so, that period's exposure exists independently of whatever happens next. Converting the role going forward addresses the future. It does nothing to resolve what already accrued.
Assessing this exposure usually means reconstructing how the relationship actually functioned before the change. Relying only on what the original contractor agreement said is not enough. Old emails, invoices, and project records can help. They can show whether the business directed day-to-day work or provided equipment. They can also show whether the person was treated as part of the internal team well before any formal conversion took place. This assessment is worth doing even when the business does not expect to find a problem. The CRA's reassessment window can reach back several years once an audit begins.
Documentation Matters: Old Terms Do Not Carry Forward
New agreements must reflect the employment relationship clearly. Old contractor terms cannot simply be carried forward into the new arrangement.
A contractor agreement was built around a contract for services. An employment agreement needs entirely different provisions. It needs a compliant termination clause, appropriate vacation and benefit terms, and clear confirmation of the new reporting structure. Simply relabelling the existing contractor agreement, without redrafting its substance, tends to produce a document that fails. Our overview of why termination clauses in Ontario often don't work explains exactly this failure pattern. A termination clause built for a contractor relationship is highly unlikely to satisfy the ESA. The ESA's protections never applied to that relationship in the first place.
Restrictive covenants need the same fresh look. A non-compete originally drafted for a contractor may already have been unenforceable under the 2021 ban. Carrying it forward into an employment agreement does not fix that. Intellectual property assignment clauses deserve a review too. IP ownership rules differ between contractors and employees by default. A poorly worded carryover clause can leave gaps in either direction.
Compensation structure often needs redrafting as well. A contractor invoice typically bills a flat project fee or an hourly rate with no source deductions withheld. An employment agreement needs to specify gross salary or wages and the pay period, and also needs to explain how statutory deductions get applied before the employee receives their net pay. Benefits and vacation entitlements need to be formalized too, if any were informally offered during the contractor period. Leaving them as an unwritten understanding risks a mismatch with what the ESA actually requires.
Why Businesses Convert Contractors in the First Place
Conversion usually starts with a concrete trigger, not a general sense that something should change.
A business might notice the working relationship has drifted toward daily supervision and fixed hours. Full integration into the team often follows. None of that fits a genuine contractor arrangement anymore. A client audit or an insurance renewal can also surface the question directly. So can advice from an accountant preparing year-end filings. Whatever the trigger, the underlying issue is usually the same. The relationship on paper no longer matches how it actually operates day to day, and someone finally noticed.
The Practical Takeaway
Conversion addresses future structure. It does not automatically resolve past exposure.
Businesses converting a contractor to an employee should treat the process as two separate tasks. The first is building a proper employment agreement for the relationship going forward. The second is honestly assessing what risk exists from the period before conversion, and deciding how to handle it. Skipping the second step does not make the exposure disappear. It just means the business finds out later, usually at a worse time than now.
Frequently Asked Questions
Does converting a contractor to an employee erase risk from the earlier period?
No. Past misclassification risk survives the conversion and remains a separate, ongoing exposure.
What new obligations apply once someone becomes an employee?
Source deductions, ESA minimum standards, and typically WSIB coverage all begin applying immediately.
Can an existing contractor agreement just be relabelled as an employment contract?
No. It needs to be redrafted, since contractor terms rarely satisfy employment law requirements.
Why does the termination clause need to be rewritten after conversion?
A clause built for a non-ESA relationship is unlikely to meet the ESA's requirements once someone is an employee.
Does a non-compete signed during the contractor period carry over automatically?
Not reliably. It may already have been unenforceable under Ontario's ban, regardless of the new status.
Who typically identifies that a contractor should be converted to an employee?
Often the business itself, after reviewing the relationship against the CRA's classification factors.
Does conversion change who owns intellectual property created going forward?
Yes. The default ownership rules for employees differ from those for contractors under Canadian copyright law.
What is the safest approach when converting a contractor to an employee?
Draft a new employment agreement from scratch, and separately assess exposure from the prior period.