Two dealership staff walking out of an open service building at sunrise with a clipboard and network cable, preparing for a Tekion implementation
Resources / Blog

Tekion Implementation Timeline: The IT Tasks Week by Week

By Erik NachbahrOctober 17, 2026 · 14 min read

A Tekion implementation timeline runs about 120 days from kickoff to go-live under Tekion’s own published plan. The dealership’s IT work, from circuits and cabling to printers, logins, integrations, and training rooms, mostly lands in the final 12 weeks, and every piece has a date.

Last updated: October 17, 2026

Picture a store 3 weeks out from its Tekion go-live. The training schedule is set, the conversion scope locked a while back, and the general manager is feeling pretty good about it. Then somebody walks the service drive with a laptop, the way the trainers will, and finds out the last 4 bays don’t get Wi-Fi. Nobody’s sure who ordered the new cabling. The electrician needs a permit first. And Tekion’s installers have a date on the calendar that isn’t moving for any of it.

None of that is Tekion’s work, and none of it has to be a surprise if you see the calendar early. Tekion runs an organized program with clear milestones, and its published Implementation Terms are straightforward about what the dealership owns. What follows is the dealer’s side of that calendar, week by week, from 12 weeks out to go-live week.

Years ago I earned my MCSE in 7 weeks, studying from books, one test a week, while I was teaching the course part-time. It worked because the schedule made the decisions for me. Every week had one thing that had to be finished before the next one could start, and I didn’t get to skip ahead. A Tekion go-live works the same way. Miss the week the network was supposed to be done and you don’t get that week back. You pay for it in go-live week.

We’ve already covered what a Tekion store needs on the network and hardware side, the IT checklist for any DMS conversion, and what happens after Tekion go-live. This piece is about when each job happens. It’s also how our Tekion enablement services team plans the dealer side of a project, before, during, and after the install.

The Tekion Implementation Timeline, From the Dealer’s Side

The Tekion implementation timeline is the schedule a dealership follows from contract kickoff to its first day live on Tekion’s Automotive Retail Cloud. Tekion describes about 120 days in 4 phases: discovery, design and build, testing and data preparation, and then training and go-live. The dealer’s IT tasks run alongside every one of them.

Those phases come from Tekion’s own article, Implementation Timeline to Success, written by its SVP of Professional Services. Kickoff and discovery run from 120 to 90 days out. Design and build carries on to 45 days out, testing and data prep to 21, and the last 3 weeks are training and launch. Here’s how the IT work lines up against it.

Weeks before go-liveTekion phaseDealer IT tasksDone when
17 to 13Kickoff and discoveryData extraction access, integration inventory, old vendor contractsEvery integration and contract is on one list
12 to 9Design and buildSecond circuit and failover, low-voltage cabling, electrical permits, Wi-Fi walkYou pull the primary circuit and the store keeps working
8 to 6Design and build, scope lock at week 6PC and printer inventory, replacements, roles and MFAEvery device and every user is accounted for
5 to 3Testing and data preparationIntegration partner notices and tests, training rooms builtA trainee can log in and print from the training room
2 to 1Training and go-liveSimulation support, hardware install, readiness sign-off, cutover planReadiness is signed by someone who walked the store
Go-live weekGo-liveLegacy access cutoff, forms and printer checks, floor supportThe first deal and the first RO print clean

The table looks tidy. Real projects aren’t. Rooftop count, the number of third-party products tied into the DMS, and the condition of your data all stretch it, and a 20-store group isn’t running one calendar. It’s running 20 of them that share the same controller and the same IT people. The order still holds.

The order is the plan.

Dealership general manager and IT manager reviewing a printed Tekion implementation project binder in the service drive

Before Week 12: The Dates Already in the Contract

Some of the earliest deadlines in a Tekion project are written into the terms before anyone has met the project manager. A complete mapping of old accounts to new ones is due in Excel no later than 120 days before go-live. The first successful extraction of data from your existing DMS has to happen no later than 100 days out. If you want conquest data converted, Tekion needs access to the source data 90 days ahead, and the conversion scope locks 6 weeks before launch.

Those sound like accounting jobs, and mostly they are. IT still ends up in the middle of them, because somebody has to get the data out of the old system. Sometimes that’s a login. Sometimes it’s a formal request to the outgoing DMS provider, or a clause in a contract nobody has read since the day it was signed. The same person should start the integration inventory, which is every product that trades data with your DMS today, from the CRM and desking tool to the parts locator and the OEM connections. The first draft of that list always comes up short. The second pass finds more. It always does.

This is also the window to pull the old agreements. If your network gear or phones came from the outgoing DMS provider, that lease may run on a different clock than the DMS contract, and the firewall configuration may belong to them. Get a copy now. If you’re still choosing a platform, our Tekion vs CDK comparison from the IT side lists what each one supplies.

Week 12 is too late to start reading contracts.

Weeks 12 to 9: Internet, Cabling, and Power

The network goes first because everything else sits on top of it. A cloud DMS is only as available as the circuit coming into the building, so this is when the second circuit gets ordered, from a different carrier if you can get one, with a firewall that switches over by itself and switches back by itself. Carriers don’t work on your schedule. They never have. Ordering a new circuit 12 weeks out isn’t early, and at some rural rooftops it’s tight.

Cabling and power run in the same window. Tekion’s terms put the full cost of required electrical work and low-voltage data cabling on the dealer, materials and permits included, along with any equipment mounted more than 10 feet off the floor. Tekion installs and tests its own hardware. That part’s covered. Your job is making sure a labeled, tested drop and a live outlet are waiting at every spot that hardware is going to go. That takes a walk-through with a floor plan at each rooftop, and a cabling contractor booked before their calendar fills up behind somebody else’s project.

Walk the Wi-Fi too, with a device in your hand, through the service drive and to the back corner of the shop. Dead spots nobody noticed on the old system start to matter when advisors and technicians work in a browser on a tablet all day. Our guide to Tekion network requirements covers bandwidth sizing in detail, so I won’t repeat it here.

Then test the failover on purpose. Pull the primary circuit on a weekday morning and watch what happens. Then plug it back in. Plenty of stores test their backup for the first time on the day they need it, and week 9 is a much cheaper day to learn it doesn’t work.

Network done by week 9, or everything after it slides.

Cabling technician running blue network cable through the ceiling of a dealership service department before a Tekion go-live

Weeks 8 to 6: Devices, Printers, and Logins

Count everything that will touch the new platform, rooftop by rooftop, down to the check printer in the office and the signature pads in F&I. Then hold each device up against what a browser-based DMS needs. Tekion runs in the browser, which convinces a lot of people that any old PC will do. It won’t. Anything still on Windows 10 has been past Microsoft’s end of support date of October 14, 2025, for a year now, and ordering, imaging, and deploying 40 replacement PCs eats most of this window. Order early. Our Windows 10 action plan for dealerships lays out the options.

Printers deserve their own afternoon. They always do. Tekion’s terms give you 5 days after launch to ask for alignment changes on local printers, and one Forms Champion at the store signs off on changes to retail forms. Five days isn’t much. Not in go-live week. So I’d print a test page now from every printer that will ever touch a deal or an RO, and swap out the ones that can’t keep up while you’ve still got time.

Then logins, which is where I’d slow down. Copying the old DMS user list is the fast way to do it, and it brings every old mistake along with it, like the manager who left in March and the shared parts login half the counter knows by heart. Build Tekion roles from what each person actually does. Turn on multi-factor authentication for everybody, general manager included. CISA calls MFA one of the simplest ways to stop an account takeover. It’s right.

Week 6 is also the conversion scope lock, and after that the data list is basically closed.

Anything not on your lists by week 6 turns up in week 0.

Weeks 5 to 3: Integrations and Training Rooms

Who tells your vendors you’re moving? You do. It’s right there in Tekion’s terms: the dealer notifies each integration partner of the transition date, and each integration has its own tasks due on its own dates. Some can’t even be tested until you’re live. A few vendors want a fee, or notice. I’d keep it simple. One spreadsheet, one owner per integration, and a phone call to every vendor on it. We’ve already seen this exact problem plenty of times. The integration nobody called is the one that breaks on launch day.

Training gets scheduled in here too. Tekion wants onsite and remote training confirmed at least 21 days ahead. Its certification program trains up to 16 Certified Professionals, up to 4 per department, and its article describes that track as a 40-hour week about 30 days before launch. Think about who those people are. They’re your best ones. They’ll be gone from their desks for a week, so somebody has to cover for them.

Now the job nobody books. Training rooms. Somebody in IT has to set up a room where 12 people can sit down, log in, and print at the same time, on a network that doesn’t buckle. In the last week or two, simulation runs on live system data, and Tekion’s article expects every employee to attend. Every one. They’ll all cycle through a room you built, so test it in week 3 with real logins, not the morning of the first session.

A training room that doesn’t work costs you the training.

IT technician connecting a network floor box in a dealership conference room set up for Tekion training sessions

Weeks 2 to 0: Simulation, Install, and Go-Live Week

At 2 weeks out, you stop building and start proving. Tekion’s installers come on weekdays during business hours, and before they arrive, you certify that every prerequisite is done. If a technician gets sent to a store that isn’t ready, there’s a trip charge and the visit gets rescheduled. Fair enough. I’d want the same rule if I were them. It does mean the person signing should be somebody who walked the store. Not whoever had the form.

Write the cutover plan down. Who shuts off the old DMS logins, and on what day does the old system go read-only? Who’s standing on the floor at each rooftop on day one, and what’s their cell number? I’d also want a page on what the store does if the circuit drops at 10 in the morning on launch day. That’s what our DMS outage plan is for. Print it before go-live.

Something won’t print on day one. I’d bet money on it. The question is how long it takes your people to reach somebody who can fix it, and at Helion the average wait for a live support agent is 82 seconds. That number matters most this week. Payroll stays open a bit after launch, because Tekion’s terms only finish the payroll piece once the second payroll batch posts to accounting, which means your office is still going to be calling IT for a few more weeks while everybody gets used to it.

Go-live is a date. Getting through it is a staffing plan.

Service advisor handing a customer a freshly printed repair order at the dealership service counter during go-live week

Who Runs the Dealer Side of the Calendar

Tekion arrives with a project manager, trainers, and a schedule. Yours should too. Your store needs one named owner who can tell the general manager on a Tuesday which tasks are late. For one rooftop, that can be your IT manager with some help. For a group sharing an IT team, I’d treat it as a full-time job until you’re live.

That’s where we come in. Helion Technologies is a Tekion Certified Partner, and for nearly 30 years we’ve done IT for automotive and heavy truck dealerships and nobody else. Today that’s 2,000-plus dealerships and 35,000 end users. We run the dealer’s side of the calendar, and we stay on after go-live to extend the momentum Tekion’s own team builds. Got your own IT team? Our co-managed IT model keeps them in charge. We add hands. On other platforms, it’s our DMS transition services. Onboarding starts within weeks of signing. The rest depends on where your store starts.

What Dealers Ask About the Tekion Timeline

Realistically, how long does a Tekion implementation take?
About 120 days, if you go by Tekion’s own published plan. Big groups take longer. So does messy data. Tekion’s article also figures on 60 to 90 days of real use after launch before the new habits stick, which means the IT calendar keeps running for a couple of months past the go-live date everybody circled.
We just signed. Are we already behind on the IT side?
Probably not, if you start this week. The account mapping deadline sits 120 days before go-live and the network work wants about 12 weeks, so the first job is putting both on one calendar and counting backward from your launch date. Start there.
Whose job is it to call our integration vendors?
Yours. Tekion’s Implementation Terms make the dealer responsible for notifying each integration partner of the transition date and completing the validation tasks Tekion provides. Put one owner next to every integration in a spreadsheet, and test the ones that can be tested before launch day.
Do we actually need a separate training room?
For simulation, yes, or something close to one. Every employee sits through several sessions on live system data in the last 2 weeks, and a room with working machines, logins, and printers keeps those hours about Tekion instead of about IT troubleshooting.
What happens if the installer shows up and we’re not ready?
A trip charge and a rescheduled visit, under Tekion’s published terms. A rescheduled install can push the whole go-live date, which is why the readiness sign-off should come from somebody who walked every rooftop.
Multi-rooftop group here. Does the order change?
The order stays the same. The volume doesn’t. Each rooftop gets its own circuit test, cabling walk, and printer check, and the shared people, usually the controller and the IT team, end up on every rooftop’s calendar at once. Map those overlaps before week 12.

Count Backward From the Date

Every week on this calendar has one job that has to be finished before the next can start, the same way my 7 weeks of tests did. The stores that get a quiet go-live are the ones that put those weeks on paper the day the contract was signed and then kept them. If you want to know which weeks your store is already behind on, start with our complimentary IT and cybersecurity assessment, and we’ll walk your rooftops and hand you the list.

The go-live date won’t wait for the network.

About the author

Erik Nachbahr

Founder & President, Helion Technologies

Erik Nachbahr founded Helion Technologies in 1997 and has spent nearly 30 years working exclusively with automotive and heavy truck dealerships. Helion now supports more than 2,000 dealerships and 35,000 end users with managed IT, cybersecurity, FTC Safeguards compliance, Tekion enablement, and managed AI, all under one team. A CISSP, Erik writes and speaks about the parts of dealership technology most operators inherit rather than choose: vendor sprawl, AI governance, and cyber risk. His goal is simple: make the technology work so dealerships can focus on what they do best, selling and servicing cars and heavy trucks.

Erik Nachbahr on LinkedIn

Confidence in your current setup and actual protection aren't always the same thing. The only way to know which one you have is to look.

Get Your Complimentary IT & Cybersecurity Assessment →