Skip to main content
GullyHR

GullyHR software · Implementation services

Implement GullyHR Around the Way Your Company Already Works

HRMS implementation is the project of getting an HR system into daily use: reviewing how your HR runs today, mapping those processes, configuring the modules to match, migrating employee data out of spreadsheets, setting roles and permissions, loading your policies and letter formats, training each user group and supporting the first live cycle. We run it as a project with a plan, not as a login and a manual.

An implementation specialist guiding two HR administrators through a laptop setup workshop.

Not sure what you need? Tell us about your business in six short steps and we will come to the first meeting prepared.

Share your requirements

HRMS Implementation Services in brief

HRMS implementation is the project of getting an HR system into daily use: reviewing how your HR runs today, mapping those processes, configuring the modules to match, migrating employee data out of spreadsheets, setting roles and permissions, loading your policies and letter formats, training each user group, and supporting the first live cycle after go-live.

  • GullyHR is an HR consulting, HR services, training and software company based in Bengaluru, working with Indian startups and small and medium businesses.
  • Implementation covers requirement analysis, process mapping, configuration, data migration, workflow and role setup, document upload, user training, go-live support and an adoption review.
  • The platform is configured to the process your management has approved: your approval routes, your entitlements, your reporting lines, not a generic default.
  • The team that builds and configures the modules runs the implementation, so there is no handover to a separate technical vendor halfway through.
  • Scope, sequence and timeline are written into a proposal after we have seen your current processes, your employee data and the modules you need.

The starting point

Has HR Software Ever Been Bought and Barely Used?

Implementations fail in the same few places: a generic set-up nobody adapted, data nobody cleaned, one training session, access nobody thought through and nothing planned for the week after go-live. The software is rarely the problem.

We run implementation as a project: analyse, map, configure, migrate, train and support.

You may be experiencing:

  • HR software bought once before and still sitting there barely used, because it was set up generically.
  • Employee data in four spreadsheets with different date formats, and everyone hoping somebody else will clean it.
  • Uncertainty about which modules to take first, and a suspicion that order matters more than the list.
  • Managers shown the system in one session and back on mail and their own tracker within a month.
  • Access never thought through, so either everyone can see salaries or nobody can see anything useful.
  • Policies, letters and forms existing as Word files with three near-identical versions and no clear owner.
  • Nothing planned for the week after go-live, which is exactly when the questions arrive.
  • A system that nobody was told how to use for their own part of the job, only shown once in a general walkthrough.
  • Approval routes in the software that do not match who actually signs off, so approvals still happen over chat.
  • Leave balances and salary components that nobody trusts after a move, because the old and new figures were never compared.
  • A promoter or finance head who wants sight of anything touching salary, and no agreed way to give it.

What we can help with

What an Implementation Covers

  • Requirement Analysis

    A working review of your current processes, data, systems and the people who run them, so nothing is configured before we know how HR actually runs.

  • Process Mapping

    Each process in scope mapped step by step, exceptions included, so the map becomes the workflow the system executes rather than a document filed beside it.

  • Platform Configuration

    Organisation structure, departments, locations, designations, reporting lines, entitlements and workflows configured to your process, not left on a default.

  • Data Migration

    Employee master data, attendance history, leave balances and salary components consolidated, loaded and reconciled against your source records before go-live.

  • Approvals and Notifications

    Each request type configured with the route it takes in practice, including who covers when an approver is away.

  • Roles and Access

    Owner, HR administrator, manager and employee roles defined against your reporting structure, so each role has the access it needs and nothing more.

  • Policies, Letters and Forms

    Your current handbook, policies, letter formats and forms collected, tidied and moved into the document centre with versions and owners.

  • Training and First-Cycle Support

    Separate sessions for each user group on the part of the system it will use, and someone available through the first payroll month, appraisal round or leave cycle.

The scope

What the Implementation Covers

These are the tasks an implementation project handles. The modules, locations and users in scope are agreed in the proposal, and the decisions on entitlements, approval limits and access stay with your management.

  1. Requirement Analysis

    Sit with the people who run HR today and look at the files and systems in use, so the modules and the order of work are agreed before anything is configured.

  2. Process Maps

    Write each process in scope as steps, approvals and exceptions, and confirm it with you, so configuration is built on an agreed picture.

  3. Organisation Set-Up

    Configure departments, locations, designations and reporting lines, so the platform mirrors how your company is structured.

  4. Entitlements and Workflows

    Configure leave entitlements and the workflow for each request type to match your process, with tests run on real cases from your business.

  5. Approval Routes

    Set the route each request takes in practice, including who covers when an approver is away and the notifications that tell an approver a request is waiting.

  6. Data Migration

    Consolidate employee master data, attendance history, leave balances and salary components from spreadsheets or an older system, load them, and reconcile against your source records.

  7. Roles and Access

    Define owner, HR administrator, manager and employee roles against your reporting structure, and confirm what each role can see, enter and approve before go-live.

  8. Policies, Letters and Forms

    Collect your handbook, policies, letter formats and forms, flag duplicates and superseded versions, and move the rest into the document centre with versions and owners.

  9. Reports

    Configure the reports you agreed during analysis, so HR can see what it needs from the first live cycle.

  10. Role-Specific Training

    Train HR administrators, managers and employees separately on the few actions each group performs, with a short reference guide for each.

  11. Go-Live Support

    Take each configured process live on an agreed date, retire the manual version for that workflow, and stay reachable through the first live cycle.

  12. Adoption Review

    After the first cycle, review what people used, worked around or ignored, and adjust entitlements, routes or forms to match.

Working together

Ways to Work With Us

  • Requirement Analysis and Demonstration

    A structured review of your processes and data, alongside a demonstration configured with your own examples.

  • Defined Implementation Project

    Configuration, migration, role setup, training and go-live support for an agreed set of modules.

  • Phased Implementation

    Modules brought live in an agreed order, usually starting with whichever process costs the most manual effort.

  • Ongoing Support

    Configuration changes, training for new users and adjustments as locations, roles, entitlements or processes change.

Where another system has to sit alongside this one, such as a biometric device, a payroll package or accounts, we say plainly what is possible before promising anything.

The deliverables

What You Receive

Depending on the modules in scope, you receive:

  • A requirement analysis and configuration plan naming the modules, processes and sequence in scope.
  • Written process maps for each HR process configured, including approvals and exceptions.
  • A configured platform matching those maps, tested against real cases from your business.
  • Migrated employee, attendance, leave and salary component data, reconciled against your source records.
  • Configured roles and permissions across owner, HR administrator, manager and employee access.
  • Your policies, letter formats and forms uploaded, categorised and version-controlled.
  • Role-specific training sessions with a short reference guide for each user group.
  • A post go-live adoption review with an agreed list of configuration adjustments.
  • A list of discrepancies found during data reconciliation, for you to close against your own records.
  • An agreed sequence for bringing the remaining modules live, where you are implementing in phases.

Step by step

How the Project Runs

  1. Analyse How HR Runs Today

    Requirement analysis and process mapping sessions with the people who run HR, written up as what was agreed, with exceptions recorded rather than ignored.

  2. Decide Entitlements, Limits and Access

    We set out workable options and the consequences of each, then configure the one you choose. Entitlements, approval limits and access are management decisions.

  3. Configure and Migrate

    Modules, workflows, roles, letter formats and reports are configured and tested against real scenarios, while data is consolidated and reconciled against source records.

  4. Train and Go Live

    Each user group is trained on what it will use, and we stay reachable through the first live cycle of each process.

  5. Review and Adjust

    After the first cycle we look at what people actually did in the system and correct the configuration where practice met the design. Where it is included in your project, we also stay reachable through the first live cycle of each process, so questions are answered while people are still learning the system.

The difference

What a Properly Run Implementation Gives You

A well-run implementation helps you:

We do not promise outcomes. We record a baseline before work starts, covering the current state of your data and how long each HR process takes today, and report against it, so you can see what changed and what did not.

  • Have a system that reflects how your business actually works, because the process was mapped first.
  • Start with employee, attendance and leave data already loaded and checked, instead of typed in over months.
  • See managers approve inside the system rather than over chat, because the route is the one they already use.
  • Match access to the reporting structure, so salary and personal data reach only the roles you decided.
  • Train each group on the few actions it needs rather than on the whole platform.
  • Fix first-cycle problems while attention is on the rollout, not after people have drifted back.
  • Know before go-live which entitlements, routes and roles were decided, and by whom.
  • Retire a spreadsheet or manual tracker for a workflow on an agreed date, instead of running both indefinitely.
  • Bring modules live in an order your team can absorb, one change at a time.
  • Review what people actually did in the system after the first cycle, and correct the configuration where practice differed from the plan.

Find your fit

Who This Service Is For

  • Companies Moving Onto GullyHR

    Businesses that have decided to move and want the platform configured around their own processes rather than switched on at a default.

  • Businesses Coming Off Spreadsheets

    Companies bringing several years of employee data out of spreadsheets, shared drives or an older system.

  • Companies Unsure Where to Start

    Businesses that want an assessment of which modules to begin with before committing to a full rollout.

  • Multi-Location Businesses

    Companies where approval routes, roles and reporting have to work across sites with different practices.

  • Businesses That Have Tried Before

    Companies that watched adoption fade last time and want the rollout run as a project.

  • Companies Redesigning HR in Parallel

    Businesses changing processes or policies at the same time, who need the system to match the new process.

  • Businesses With Several Spreadsheets of Employee Data

    Companies whose employee data sits in different files and formats and needs to be consolidated and checked.

  • Owners Who Want to Approve Salary-Related Changes

    Businesses where a promoter or finance head wants sight of anything that touches salary.

  • Teams With a Small HR Function

    Companies where one or two people run HR and cannot absorb a long, unplanned rollout.

Good to know

How It Fits Your Workflow

Who does what during the project

  • HR gives us access to the current files, systems and the people who run each process.
  • Management decides entitlements, approval limits and who may see what, and confirms them in writing.
  • We map, configure, load your data and test against real cases.
  • HR reviews the configuration and the migrated data and signs off before go-live.

After go-live

  • Employees and managers use the parts of the system they were trained on.
  • HR owns day-to-day operation, data accuracy and any decision to change a policy or a route.
  • We review the first cycle with you and adjust the configuration.

Each configured process goes live on an agreed date, and the manual version for that workflow is retired.

Good to know

What You Can Track

Before go-live

  • Data reconciliation: the loaded employee, attendance, leave and salary component data compared with your source records, with discrepancies listed.
  • Baseline: the state of your data and how long each HR process takes today, recorded before work starts.

After the first cycle

  • What people actually used in the system.
  • Where they worked around it, and which entitlements, routes or forms were adjusted as a result.

Reports for each module are described on that module's own page and configured as agreed in your scope.

Good to know

What It Is and Is Not

What an implementation is

  • A defined project with an agreed scope, sequence and acceptance point, set out in a proposal.
  • Configuration of the GullyHR platform to the process your management has approved.
  • Run by the team that maps, configures and trains, so there is no handover to a separate vendor partway through.

What it is not

  • It does not make your decisions. Entitlements, approval limits and access are yours.
  • It does not fix an unsettled process by configuring it. Process redesign is a separate scope within our HR process consulting.
  • It does not assume a connection to a biometric device, payroll package or accounts system. We assess what can be exchanged and scope any specific integration as separate work.

The software is separate from our consulting and services, and each is scoped on its own.

Good to know

Getting Started

What you bring

  • Your employee data, in whatever state it exists, from spreadsheets, files or an older system.
  • Your current policies, handbook, letter formats and forms.
  • Your approval routes as they run in practice, including who covers when an approver is away.
  • Decisions on entitlements, approval limits and which roles may see salary data.
  • A named person who can give us access to the people who run HR.

Support

Data does not need to be clean before we start. Cleaning is part of the project. The time we need from your team depends on the modules, locations and employees in scope, and the proposal names who is needed at each stage.

Good to know

Access and Data

Who sees salary and personal data

Access is configured by role during set-up and reviewed with you before go-live. Only the roles you decide can see salary and personal data, and the roles can be adjusted later as your structure changes.

Your data during the project

The project involves employee and salary data. Before work starts we agree what data we need, who handles it and how it is shared. The terms are set out in the agreement for your engagement.

Good to know

Frequently asked questions

A defined project: requirement analysis, process mapping, configuration, data migration, roles and permissions, document set-up, training for each group and support through the first live cycle. The scope states which modules and locations are included before anything starts.

Put the System Into Daily Use, Not Onto a Shelf

Map how HR actually runs, configure the platform to match, load clean data and train each group, then stay for the first cycle.

Prefer to talk first? Call +91 80958 58589 or write to hello@gullyhr.com.

Book a Personalised Demo

Tell us what you want to move into the system.

Your next chapter

Let’s make HR work better.

Tell us what is slowing your team down. We’ll help you find a practical way forward, starting with a conversation.

  • A free first conversation with an HR practitioner
  • A clear scope and fee before any paid work
  • A practical next step for your business

Let’s start with your business

Share your contact details and the HR challenge on your mind. We’ll help you find the right starting point.

10-digit Indian mobile, without +91.

Your details stay private. Privacy policy