Skip to content
Contact Book a call

Our delivery process · Zoho, AWS, Shopify, WordPress · Los Angeles, CA

How we run Zoho projects and migrations step by step

Starting fresh and moving off another tool begin at the same place: a free call with our founders. From there the routes split. A new build runs on 12 steps. A move to Zoho runs on 15, because your old system has to keep working until the new one has proved itself. Both routes end at go-live with your team trained.

New project: we map how you work, agree the scope in writing, then build, test and train.

Book a discovery call Walk the steps
Zoho Advanced PartnerZoho rollouts and moves since 2025
You’ll talk to our senior team, not a call center.300+ projects · serving US clients since 2025

01Choose a track, then your role

Where do I come in?

Showing all 12 steps of a new project.

The 12 steps of a new Zoho project

Every Zoho, AWS, Shopify or WordPress build we take on follows this line. Four phases, twelve stops, and two documents you sign before anything gets built: the BRD and the delivery schedule.

  1. Phase 1 · Plan

    01Free

    Discovery call

    What happens
    Thirty minutes on video about what you want fixed, the software you pay for today and any date you’re racing.
    Who’s involved
    You, plus Ikramul or Khris from our side.
    You get
    A written recap with the next step we’d suggest.

  2. 02

    Workflow mapping

    What happens
    We sit with each department and trace how work moves: who types what, where it stalls, which spreadsheet patches the gap.
    Who’s involved
    Department heads and a couple of hands-on users; our consultant runs the sessions.
    You get
    A process map per department, written in your team’s words.

  3. 03

    Scope & budget

    What happens
    The maps become a scope: platforms, modules, integrations, and license costs at the vendor’s list price. Larger projects sometimes need a paid scoping phase, and we price that before it begins.
    Who’s involved
    The project owner and whoever holds the budget; our founders and project lead.
    You get
    A scope summary and our fixed fee for the work. Anything you add after the BRD is signed gets quoted as a change for your approval.

  4. 04You sign

    BRD sign-off

    What happens
    Fields, automations, reports, integrations, data imports and the checks that prove each one works all go into the BRD (business requirements document).
    Who’s involved
    Each department head approves their section; the project owner signs the whole thing.
    You sign
    The BRD, with our fee fixed inside it.

  5. Phase 2 · Set up

    05

    Kickoff

    What happens
    One meeting to name the people on both sides, settle who approves what, hand over system access and agree how we keep in touch.
    Who’s involved
    Project owner, department heads, our project lead.
    You get
    A contact sheet and a written communication plan.

  6. 06Before any build

    Delivery schedule

    What happens
    Each module and integration is given a date, so you can see the finish line on day one of the build.
    Who’s involved
    Our project lead drafts it; the owner and department heads check it against holidays, busy seasons and staff time.
    You get
    The schedule, kept current as the work moves.

  7. 07

    Sprint plan

    What happens
    The schedule is cut into short sprints. Each one has a builder on our side and a reviewer on yours.
    Who’s involved
    Our project lead, with the department heads who will review each sprint.
    You get
    A sprint list showing who checks which piece.

  8. Phase 3 · Build

    08

    Build

    What happens
    Our consultants configure and develop in Zoho, AWS, Shopify or WordPress, and add AI (now also called SI, super intelligence) agents where they save real hours.
    Who’s involved
    Our consultants and developers. Your department heads answer questions as they come up.
    You get
    Working screens to click through at the next demo.

  9. 09Every 1 to 2 weeks

    Review demos

    What happens
    Weekly or bi-weekly, we show what’s finished inside your own account and collect changes while they’re still small.
    Who’s involved
    Department heads and the users who’ll live in the system.
    You get
    Demo notes, plus draft manuals and short videos as features land.

  10. 10

    Testing

    What happens
    Our QA goes first. Then your users run their daily tasks against the acceptance checks written in the BRD.
    Who’s involved
    Team members test; department heads confirm their area passes.
    You sign
    A test sign-off for each department.

  11. Phase 4 · Launch

    11Included

    Training

    What happens
    Hands-on sessions by department, at your office in Southern California or over video anywhere else.
    Who’s involved
    Everyone who will use the system, grouped by role.
    You get
    Manuals and recorded videos your new hires can use later.

  12. 12

    Go-live & support

    What happens
    We switch it on, watch the first weeks closely, fix whatever real use turns up and plan the next round of improvements.
    Who’s involved
    Your whole team, with our project lead on call.
    You get
    A go-live checklist and a named support contact.

Leaving Salesforce, HubSpot, QuickBooks or another tool instead? Switch to the migration track →

The 15 steps of a migration to Zoho

Moving a running business needs extra stops: a renewal check, a migration BRD, a sample move that each department signs off, a catch-up pass and a careful goodbye to the old tool. The seven stops marked as interchanges exist only on this line.

  • Migration-only stop
  • Same stop as a new project

  1. Phase 1 · Plan the move

    01Free

    Discovery call

    What happens
    Your goals, the tools you want out of, which departments use them and roughly how many people log in.
    Who’s involved
    You and one of our founders.
    You get
    A recap that names the route and the likely next step.

  2. 02Migration only

    Timeline & renewal check

    What happens
    For every subscription you’re leaving we note when it ends, the notice it needs and how its data can be exported. Then we set its stopper date.
    Who’s involved
    The project owner or finance lead, with our project lead.
    You get
    A renewal sheet listing every stopper date.

  3. 03

    Migration plan

    What happens
    What can realistically move inside the window, which department goes first, what gets rebuilt in Zoho and which cutover option suits you.
    Who’s involved
    Project owner and department heads; our founders and project lead.
    You get
    The plan, with a fixed fee for the move.

  4. 04Migration only

    Migration BRD

    What happens
    Every object and field per department, the field map, the rebuild list, stopper dates, what each department has to confirm, acceptance checks (record counts and sample records), and the cutover and rollback plan. On larger moves this is often what the paid Migration Assessment delivers, credited in full; on smaller ones it follows straight after the plan.
    Who’s involved
    Our consultants write it with each department head.
    You get
    The Migration BRD, ready for sign-off.

  5. 05Migration onlyYou sign

    Department sign-off on the BRD

    What happens
    Each department’s SPOC (single point of contact, usually the department head) signs their section. The overall project owner signs last.
    Who’s involved
    Every SPOC plus the project owner.
    You sign
    The Migration BRD. Each signature is recorded.

  6. Phase 2 · Get ready

    06

    Kickoff

    What happens
    Team, roles, access and the communication plan, plus the data-freeze rules everyone follows during cutover.
    Who’s involved
    Project owner, SPOCs, our project lead.
    You get
    A one-page freeze rulebook for cutover week.

  7. 07Counted back

    Delivery schedule

    What happens
    Dates per department and module, each one placed well ahead of the stopper date it answers to.
    Who’s involved
    Our project lead, checked by the SPOCs.
    You get
    A schedule where every row shows its spare days.

  8. 08

    Zoho setup & development

    What happens
    Modules, fields, layouts and the rebuilt automations are finished before a single record lands, and you see them in review demos.
    Who’s involved
    Our consultants; SPOCs review.
    You get
    An empty Zoho that already works the way you do.

  9. Phase 3 · Prove it

    09Migration only

    Sample migration

    What happens
    A representative slice from each department goes into Zoho first, including the awkward records: old ones, huge ones, ones with attachments.
    Who’s involved
    Our consultants run it; SPOCs choose what goes in the sample.
    You get
    Your own records, live in Zoho, to inspect.

  10. 10Migration onlyYou sign

    Department sign-off on the sample

    What happens
    Each SPOC opens their sample in Zoho, compares it with the old tool and confirms. The bulk move waits for every department.
    Who’s involved
    SPOCs, often with a team member who knows the records best.
    You sign
    A sample sign-off per department, kept on record.

  11. Phase 4 · Move and test

    11Migration only

    Full migration + catch-up pass

    What happens
    Everything moves. A catch-up pass then copies anything your team changed in the old tool since the main run.
    Who’s involved
    Our consultants; SPOCs spot-check.
    You get
    A validation report with before and after counts for every object.

  12. 12

    Testing (UAT)

    What happens
    Department users do their normal day in Zoho on migrated data and log anything odd.
    Who’s involved
    Team members, with SPOCs approving the result.
    You sign
    User acceptance per department.

  13. 13Included

    Training

    What happens
    Department by department, on records people recognize, so the first morning in Zoho feels familiar.
    Who’s involved
    Every user of the old tool.
    You get
    Written manuals and recorded videos per department.

  14. Phase 5 · Switch over

    14Before the stopper date

    Cutover & go-live

    What happens
    Zoho becomes the system of record. The old tool turns read-only, and the rollback window we agreed starts counting.
    Who’s involved
    Everyone, following the freeze rules from kickoff.
    You get
    A go-live note confirming what switched and when.

  15. 15Migration only

    Hypercare & decommission

    What happens
    Close support while the team settles in. Your old subscription is canceled only once you tell us you’re happy.
    Who’s involved
    The project owner gives the final word; our project lead handles the rest.
    You confirm
    The decommission, in writing.

Routes we’ve written up in detail

Leaving a different tool? See every route to Zoho →

Starting with nothing to move? Back to the new project track →

02Paperwork you keep

What you get at every step of a Zoho project

Something written you can hold us to. Each document below lands at a known stop on the line, and it stays yours after go-live. The tag shows which track produces it.

  • New projectStep 4

    BRD

    Requirements per department, integrations, data imports, the checks that prove each item works, and our fixed fee.

  • MigrationStep 4

    Migration BRD

    Field map, rebuild list, stopper dates, acceptance checks, plus the cutover and rollback plan.

  • Both tracksStep 6 or 7

    Delivery schedule

    A date for every module and integration. On a migration, each date is counted back from a stopper date.

  • Both tracksBRD and testing

    Sign-off sheets

    Who approved what, and on which date: every department SPOC first, then the overall project owner.

  • MigrationStep 10

    Sample sign-off

    Each department’s test records, checked side by side with the old tool and confirmed before the bulk move.

  • MigrationStep 11

    Validation report

    Record counts before and after for every object, with spot checks on individual records.

  • Both tracksDemos and training

    Manuals + recorded videos

    Written guides and screen recordings for each department, ready for the next person you hire.

03Names on the page

Who signs off a Zoho project, on your side and ours?

On your side, one person per department plus one person for the whole project. On ours, the founders who agree the fee and the people who do the work. Everyone knows from kickoff which signatures are theirs.

Your side

  • Overall project ownerSigns the full BRD, confirms go-live and, on a migration, gives the word to cancel the old tool.
  • Department SPOCUsually the department head. Signs their section of the BRD and, on a migration, their sample. The first person we ask about anything in their area.
  • Team membersTest with real tasks and join training. No signatures, but their feedback shapes what the SPOC signs.
  1. BRDBefore anything is built
  2. SampleMigration, before the bulk move
  3. TestingBefore go-live
  4. DecommissionMigration, after you’re settled

Our side

  • FoundersIkramul Karim (Co-Founder & CEO) and Khris Kakosimidi (Co-Founder & CFO) take the first call and agree the fixed fee with you.
  • Project leadYour day-to-day contact. Owns the schedule, runs the demos and collects every sign-off.
  • Consultants and developersCertified Zoho consultants from our 40+ person team who map, build, move data and train.

04Hold us to these

Five commitments on every Zoho project and migration

They apply whichever track you’re on, and four of them are written into the BRD you sign. The fifth only matters when you’re leaving another tool, and it matters a lot.

  • 01Fixed priceAgreed in a signed BRD before work starts. New requests after that are priced as changes you approve first.
  • 02Schedule before buildEvery module has a date on paper before our consultants touch your account.
  • 03Demos every week or twoYou see real progress in your own system, weekly or bi-weekly.
  • 04Training includedOn-site in Southern California, online across the US, Canada and Latin America.
  • 05Your old tool stays onLive, then read-only, until you confirm Zoho is working. Migration track.

05Process questions

Questions about how a Zoho project runs

Timing, cost, signatures and what happens to the system you’re leaving. Ask the rest on the first call; it costs nothing.

Book a discovery callSee the documents →

How long does a Zoho project take?

It depends on how many departments, integrations and records are involved. The real answer is written into your BRD as a delivery schedule, with a date for every module, before any build work starts. On a migration, those dates are counted back from your stopper date.

Is the first call free?

Yes. The discovery call with one of our founders is free and carries no obligation. You leave with a written recap and a suggested next step.

Is the Migration Assessment paid?

Yes. On larger moves we often start with a paid Migration Assessment that produces the Migration BRD, and its fee is credited in full against your migration. We quote it before it starts. Smaller moves often go straight from the plan to the BRD.

Can we start with one department?

Yes. We can scope one department or one app first, go live, then add the next phase on the same process with its own BRD.

Who signs the BRD?

Each department SPOC, usually the department head, signs their section, and the overall project owner signs the whole document. We record every signature.

What is a stopper date?

It is the last safe day to still be working in a tool you are leaving. We set it before the contract end date so there is room for notice, the final export and a rollback window, and we set one per product.

What happens to our old system after go-live?

It becomes read-only on cutover day, so nothing is lost and nobody keeps working in two places. We only cancel it after you confirm that Zoho is working for every department.

How often will we see progress?

Every week or every two weeks, in a review demo inside your own account. Draft manuals and short videos arrive as features are finished.

Is training on-site or online?

Both. We train on-site for teams in Southern California and online for teams elsewhere in the US, Canada and Latin America. Training is part of the fixed fee and comes with manuals and recorded videos.

Do AWS, Shopify and WordPress projects follow the same steps?

Yes. The 12-step new project track is the same whether we are building in Zoho, AWS, Shopify or WordPress. The 15-step track is for moving a business off another tool and into Zoho.

What is SI?

SI stands for super intelligence. In September 2026 a US executive order asked federal agencies to use “super intelligence” or “SI” in place of “artificial intelligence” in official communications. Most businesses still say AI, so we use both terms.

06Let’s talk

Tell us what you’re building. We’ll map the fix.

Book a free consultation with Elite Tech Global. We review your Zoho, AWS, Shopify or WordPress setup, show where AI / SI agents can save time, and agree the next step. If we work together, every requirement and a fixed price go into a signed BRD before the build starts.

Real people, one team. Led by co-founders Ikramul Karim and Khris Kakosimidi, and a 40+ member team across Zoho, AWS and AI.

Get your free consultation

Tell us a little and we’ll reply with next steps.

What can we help with?

No spam. We use your details to reply about your project, and send occasional updates only if you tick the box above. See our Privacy Policy.