Selection, configuration, data migration and rollout of ERP, CRM, HRMS and accounting platforms
ERP and CRM implementation covers platform selection, configuration, customisation, data migration and staff training for Zoho, Odoo, ERPNext, HubSpot, HR, helpdesk and accounting software used by growing teams. Sales, stock, accounts and HR share one record.
- Platform recommended from a requirement and gap study
- Data cleaned, migrated and reconciled against existing books
- Role-wise training, phased rollout and support after go-live
GullySystem configures, customises and rolls out CRM, ERP, HRMS, accounting, inventory and helpdesk platforms for distributors, manufacturers, clinics, logistics operators, professional firms and multi-branch service companies. Some engagements restart stalled rollouts. The licences were already bought.
Where Business Software Falls Out of Use
Licences Without Active Users
Seats are renewed every year, yet only a few people open the system, while the rest work in spreadsheets and chat groups. The platform ends up holding a partial, out-of-date record of customers, quotations and stock movements, and it grows staler with each renewal. Nobody trusts it.
CRM Stages That Differ From the Sales Process
Default stages are generic. Representatives skip them or fill in half the details, so the pipeline report loses credibility in every review meeting. Forecasts turn into guesses.
Licensed Modules That Were Never Configured
A licence may cover purchase, stores and accounts. Only billing is set up. Item lists, units of measure and opening stock are missing, so the stores team keeps a paper register beside the paid system, filled by hand.
Data Loaded Incorrectly at Cutover
Records loaded in a hurry carry the same customer under several spellings, missing tax IDs and opening balances that do not match the ledger. Staff keep the old sheet. It holds the figures they trust.
Approvals Handled Outside the System
Many platforms include an approval workflow, but limits, roles and routing are left unconfigured, so every user can do everything. Discounts and purchase orders get cleared by phone. Nobody records who agreed to what, or when.
Standard Reports and Shared Admin Screens
Reports run as shipped. No dashboard exists per role. The owner, the sales head and the accountant open the same admin screen and export it to Excel, where each builds a private version of the numbers.
Training Held Once Before Go-Live
One demo covers every department, so each team sits through screens that belong to another. New joiners copy the person beside them. Wrong entries pile up in fields that nobody ever understood, and cleanup falls to accounts.
The work covers configuring a platform you already license, or choosing one before purchase. In both cases the build follows how the company actually trades, starting at the first enquiry and ending with the receipt for the final payment.
A Platform Configured Around the Way the Business Runs
Implementations stall at configuration and adoption. The software is rarely the cause. The work starts from the enquiry-to-payment flow, the approval limits and the reports management reviews. The platform is then configured around them. It may be Zoho, Odoo, ERPNext, HubSpot, an HRMS, a helpdesk or a custom-built ERP where no product fits. Gaps are extended.
Fit Study Before Purchase
A department-by-department requirement and gap study sets out what the platform handles as standard, what needs configuration, what needs custom work and what stays outside the system. The result is a written basis for the decision. Nothing is assumed.
Data Cleaning and Reconciliation
Records are de-duplicated, standardised and mapped before migration, then reconciled against existing ledgers and registers so that opening balances and customer histories match. Nothing moves across on trust.
Rollout With Training
Roles, screens and reports are set up per department. Rollout runs one team or branch at a time, with training sessions and a supported go-live period for the first real transactions.
What Changes After an Implementation
Focus on business value before discussing technology.
Workflows That Follow the Process
Pipeline stages, forms, fields and document formats use the names that the sales, purchase, stores and accounts teams already use. Data entry follows the work as it happens. It does not wait for the evening.
Data Ready for Reporting
Duplicates are merged, formats are standardised and balances are reconciled before cutover, so receivables and pipeline reports draw on checked records. Month-end stops being a hunt through old sheets.
Modules Configured Together
Purchase, stores, sales and accounts modules are configured and switched on as a set, so one record carries the order, its stock movement, its invoice and its payment. No re-keying between screens.
Defined Roles and Approval Limits
Discount authority, purchase approval values and cost price visibility are set inside the system, and a trail of each decision stays attached to the record it approved. Disputes end quickly.
Role-Based Dashboards
Pipeline, dispatch status and outstanding payments appear on dashboards set per role, so reviews begin from figures already on screen and nobody waits for an emailed export. Spreadsheets stay closed.
Phased Rollout by Team or Branch
One department or branch goes live first and settles before the next begins, and billing and dispatch carry on through the project with no freeze on invoices. Stock never goes unrecorded.
What Is Implemented and Configured
Everything required from operational discovery to production deployment and long-term maintenance.
Requirement and Gap Analysis
Work across sales, purchase, stores, finance and HR is mapped as it runs today, then compared line by line with what each candidate platform does as standard.
Platform Selection and Recommendation
A shortlist sets out fit, configuration effort, licence model and remaining custom work in plain terms, so the client can compare options without reading vendor brochures. The decision stays with the client.
ERP Implementation and Customisation
Company masters, item and warehouse structures, tax setup, document numbering, workflows and custom modules on platforms such as Odoo or ERPNext. Testing comes first.
Custom ERP Development
Some production flows, pricing models and trade practices fit no package, so modules are built around them and the operation does not have to bend to the software. Nothing is forced.
CRM Implementation and Pipeline Configuration
Zoho CRM, HubSpot, Odoo CRM and similar platforms are configured with real stages, territories, dealer structure, quotation formats and follow-up rules that match how representatives sell.
HR and Attendance Rollout
Employee masters, attendance and shift capture, leave policies, branch hierarchies and payroll inputs, configured for teams spread across several locations and supervised by local managers.
Finance and Accounting Software Setup
Chart of accounts, sales tax or VAT configuration, invoice and voucher formats, and a working link between the operational system and the books kept in QuickBooks or Zoho Books.
Inventory and Warehouse Configuration
Multi-warehouse stock, batch and serial tracking, reorder levels, stock reservation against confirmed orders and physical-count reconciliation, so the quantity on screen matches the quantity on the shelf. Counts get checked.
Project, Helpdesk and Applicant Tracking Implementation
Project and task tracking, service ticketing with response-time targets and technician assignment, and applicant tracking for companies that hire in volume and lose candidates in inboxes.
Data Migration and Cleansing
Spreadsheets and legacy records are extracted, de-duplicated, standardised and mapped to the new structure, and totals are reconciled before cutover. Any mismatch goes back to its owner.
Integrations With Existing Systems
The platform connects to accounting software, messaging, payment gateways, the website and any in-house application already in use. Ready connectors are used where they exist. Small custom ones fill the rest.
Training, Go-Live Support and Maintenance
Role-wise sessions, plain-language guides and a supported go-live period come first. Configuration then keeps changing as the business changes shape, with new users and branches added whenever the team grows. Support stays.
Typical Implementation Situations
Real-world business processes we configure and automate.
A CRM Licence Not Used by the Sales Team
A solar EPC company has CRM seats for its field team. The default stages of lead, opportunity and closed do not match a sale that runs through survey, design, proposal and subsidy paperwork. The stages are renamed to match. Only the fields a representative actually holds at each point are mandatory, and territory-wise assignment and mobile screens for site visits are added. Unused screens are hidden.
Modules Licensed but Not Switched On
A light-engineering manufacturer holds a full ERP licence, yet only billing is configured. Purchase, stores and quality stay on registers because item masters, units of measure and opening stock were never built. The masters are created, along with document numbering, stock reservation against confirmed orders and goods-receipt matching. Then each module goes live in turn.
Years of Client Sheets Moved Into One System
An architecture and interiors practice keeps client, project and billing history across many workbooks. The same client appears under several spellings, tax IDs are missing and dates use mixed formats. Fields are mapped and records are de-duplicated. A trial migration runs in a test environment, and counts and outstanding amounts are reconciled with the partners before cutover. The old workbooks stay read-only.
Purchase Approvals Set by Value and Category
A food-processing company with several units approves consumable and machinery purchases through phone calls between the unit head and the director, and the auditor cannot see who cleared what. Approval routing is configured by value slab and purchase category, with limits set against roles rather than individuals, which keeps the matrix valid when people change jobs. Phone approval is enabled. Each decision leaves a trail.
HRMS Rolled Out Depot by Depot
A logistics operator has drivers and loading staff across several depots, and attendance registers arrive as photographs at month-end. Employee masters, shift rosters, leave rules and payroll inputs are configured centrally. The rollout then runs depot by depot, with the local supervisor trained before that depot goes live. Photographs stop.
A Stalled Rollout Restarted
A garment retail chain bought an ERP, went live on billing only and drifted back to a parallel stock sheet at each store. The existing configuration and data are audited, then item masters and the store hierarchy are corrected and purchase and stock setup is completed, with badly loaded records cleaned. Store staff are retrained role by role. The licences stay in use.
Is This Service Right for Your Business?
We partner with established businesses that have outgrown manual processes and want reliable systems.
Companies Adopting a First Business System
Businesses that have outgrown spreadsheets and accounting software and now want sales, stock and approvals inside one platform, with every department reading the same customer and item records.
Teams Whose Platform Was Never Adopted
A CRM, ERP or HRMS is already licensed, but configuration was only partly done, data was loaded as it came and the team drifted back to earlier habits.
Multi-Branch and Multi-Location Operators
Distributors, clinic groups, depots and retail networks where head office collects figures from each branch by email and merges them by hand. One set of records replaces several.
Businesses With Separate Departmental Tools
Sales sits on one tool, stores on a register, accounts in accounting software and HR on paper. A reconciliation exercise comes before each management decision, and it delays every one of them. Nobody owns the full picture.
Cases Where an ERP Is Not Yet Needed
A small team at one location with a few orders a day and one product line may find that licence cost and training effort outweigh the benefit. A shared database or one automation often fits better. This is said in the first conversation.
Cases Where a Package Is the Wrong Fit
Some businesses run a pricing model, job-work flow or trade practice that no packaged product supports, and forcing a package produces continuous workarounds. A custom-built system is then recommended over configuration.
Enterprise Capabilities in Plain Business Terms
Role-Based and Field-Level Permissions
Permissions are assigned per role. A salesperson sees their own pipeline rather than the whole team’s, while cost prices, margins and salaries stay with the roles that need them.
Custom Fields, Forms and Modules
Fields and screens are added where the standard product stops short, with every change documented so a later administrator can follow it.
Sales Pipeline and Stage Rules
Custom stages, mandatory fields, follow-up reminders and automatic assignment by territory or product line, so no enquiry waits unowned in a shared queue.
Multi-Level Approval Matrices
Sequential or parallel approvals for discounts, purchase orders, expenses and leave, driven by value and category, with every limit attached to a role instead of a named person.
Multi-Branch and Multi-Warehouse Setup
Separate branches, warehouses and cost centres sit under one consolidated management view for the director, while each branch manager sees only their own books.
Tax and Document Configuration
Tax rules, product tax codes and place-of-supply handling, invoice numbering series and print formats are configured to the business’s tax position. What applies to it remains a question for its accountant.
Data Cleansing and De-Duplication
Duplicate customers and items are merged and formats are standardised, so records are corrected before they enter the new system and not after.
Reports and Role-Based Dashboards
Separate landing screens for the owner, the sales head, the accountant and the store keeper, each showing only the figures that person acts on.
Messaging Templates Inside the Platform
Quotation, order confirmation and payment-reminder templates, sent over email, SMS or WhatsApp from inside the system and logged against the customer record.
Mobile Access for Field Staff
Smartphone screens for representatives, technicians and drivers who work away from a desk, covering visit logs, job cards and proof of delivery.
Audit Trail and Change History
Every transaction carries a record of who created, edited or approved it, kept for disputes and audits. Nothing is overwritten silently.
User Provisioning and Backups
Joiner and leaver handling, environment setup and scheduled backups of configuration and data, so a departed employee never keeps access.
Our Structured 6-Step Delivery Process
A transparent path from your first conversation to a reliable production release.
- 01
Discovery and Process Study
Sessions with the people who do the work in sales, stores, accounts and HR document how an enquiry becomes an order and an order becomes a payment. The client provides access to those staff, plus samples of real documents such as quotations, invoices, stock registers and salary sheets.
- 02
Requirement Planning and Platform Decision
A gap analysis records what the shortlisted platforms do as standard, what needs configuration, what needs custom development and what stays outside the system. The client signs off the platform and licence plan. Purchase follows.
- 03
Configuration and Solution Design
Masters, pipeline stages, approval limits, roles, tax rules and document formats are built in a test environment, and the client reviews the design with live examples before confirming it. Migration begins after that. No exceptions.
- 04
Data Migration and Customisation
Existing records are cleaned, mapped and trial-migrated, then counts and balances are reconciled with the books, and custom modules and integrations are built in this stage. Each data set needs one named owner on the client side to confirm the figures before any balance is accepted as correct.
- 05
Testing, Pilot and Go-Live
A pilot team or branch runs real transactions while the old method continues in parallel, and faults are fixed until the client accepts against the agreed checklist. Cutover happens on a planned date. A rollback option stays ready.
- 06
Training, Adoption and Support
Role-wise training sessions, short guides in plain language and a supported go-live period cover the first real questions from the team. Support then continues. Changes, new users and new branches are handled as they arise.
What You Receive Upon Project Completion
Everything required to run, maintain, and expand your software without vendor lock-in.
Connects With the Systems You Already Rely On
We build bridges between your software so you don't have to replace functional existing tools.
ERP & Business Platforms
- Odoo
- ERPNext
- Zoho One
- SAP Business One
- Microsoft Dynamics 365 Business Central
CRM & Sales Platforms
- Zoho CRM
- HubSpot
- Odoo CRM
- Freshsales
- Salesforce
Accounting, HR & Helpdesk
- Xero
- Zoho Books
- QuickBooks
- BambooHR
- Zoho People
- Zoho Desk
- Freshdesk
Communication & Messaging
- WhatsApp Business API
- Gupshup
- Twilio
Payments & Workplace Tools
- Stripe
- Google Workspace
- Microsoft 365
Selected for Reliability, Speed, and Longevity
Technology chosen to match your operational scale and long-term maintainability.
Platform Customisation
Custom Modules & APIs
Databases & Migration Scripting
Reporting & BI
Hosting & Operations
Why Business Owners Choose GullySystem
Recommendation Based on a Gap Study
Platform advice comes from the requirement and gap analysis. If the system already licensed can do the job with proper configuration, that is the recommendation, and replacement is not.
Configuration in the Client’s Vocabulary
Stages, fields, document formats and report names follow the terms staff already use on the shop floor and on the phone. Screens read the way the work is described.
Data Reconciled, Not Only Uploaded
Migration is finished only when counts and balances tie back to the registers and ledgers used before. Go-live waits for that tie-out. Pressure to start does not change this.
Adoption Included in Delivery
Training, phased rollout and a supported go-live period are part of the scope, but data entry for the client’s team after handover is not. If staff do not use the system, configuration alone cannot change that. This is discussed before signing.
Configuration and Custom Development Together
GullySystem also develops software, so the point where configuration should stop and a custom module should start can be judged directly. Nothing gets bent to avoid writing code.
Support After Go-Live
Many requests appear after launch, once staff use the system properly, and changes, new users and additional branches are handled after go-live without waiting for a fresh project. Real use shows what was missing.
Flexible Engagement Options
Choose an engagement model that matches your operational scope, budget, and timeline.
Selection and Requirement Advisory
A focused requirement and gap study with a platform shortlist, configuration effort estimate and licence plan, suited to companies where the platform decision is still open. Nothing is configured yet.
Full Implementation Project
One platform, agreed modules and agreed branches, with configuration, migration, integration, training and go-live. Each phase ends at an acceptance point. The client signs it before the next one starts.
Phased Departmental Rollout
Sales goes first, then purchase and stores, then finance and HR. Each department settles before the next begins, so no team is ever trained on a half-built system or asked to guess.
Post-Implementation Support
Continuing support for configuration changes, new reports, additional integrations, user onboarding and new branch rollouts as the business grows beyond the first setup.
Frequently Asked Questions
Straightforward answers to the questions owners ask before getting started.
Should a small business choose a ready ERP or CRM, or a custom one?
It depends on the requirement and gap study. Processes are mapped across departments and platforms that cover most of them as standard are shortlisted, with a custom-built system recommended where none fits. Fit, configuration effort, licence model and remaining custom work are set out as trade-offs. Licences are bought from the vendor in the client’s name.
Can you customise the platform we already use instead of replacing it?
Yes. The current configuration, masters and data quality are reviewed first. The review separates what configuration can fix, what needs a custom module or extension and what the platform cannot do. Replacement is recommended only when the gap is structural.
Can you migrate our data from Excel and accounting software?
Yes. Spreadsheets, accounting software, legacy databases and exports from an older system are all usual starting points. The work covers far more than upload. Customers and items are de-duplicated, formats and codes are standardised, fields are mapped and a trial migration is run, then counts and balances are reconciled before cutover.
Will you integrate the system with accounting software and WhatsApp?
Yes. Accounting sync with QuickBooks, Xero or Zoho Books and messaging through the WhatsApp Business API are common integrations, alongside payment gateways, website enquiry forms and in-house applications. A ready connector is configured where one exists. Otherwise one is built and maintained.
What drives the cost of an implementation?
Cost depends on the departments and modules in scope, the customisation beyond standard behaviour, the users and branches rolled out, the state of existing data and the integrations needed. Licence fees are separate and paid to the platform vendor. The implementation figure is confirmed after discovery, in a proposal broken down by scope item, so any single part can be deferred or dropped. No lump sums.
What decides how long it takes?
Duration depends on scope and on how quickly decisions and data arrive from the client. A single-department CRM configuration is short. A multi-module ERP across branches, with heavy data cleaning and custom modules, runs longer, and slow data confirmation is the most common cause of delay. A dated phase plan follows discovery.
Our earlier implementation stalled. Can you take it over?
Yes. Taking over a half-finished or unused rollout is regular work. The current configuration, masters and data are audited, and the audit lists what is wrong and what can be kept. The setup is corrected and badly loaded data is cleaned, then adoption restarts with role-wise training. Existing licences are usually kept.
How do you train our users?
Training is role-wise, not one session for everybody. A sales representative learns the visit and quotation flow, the accountant learns invoicing and reconciliation, and the store keeper learns receipts and issues. Each role gets a short guide in plain language. Support continues through the first weeks of live use.
Do you support us after go-live?
Yes. Each implementation includes a supported go-live period. An optional ongoing arrangement then covers configuration changes, new reports and dashboards, integrations, new users and further branches as they come up.
Who owns the configuration, the data and any custom code?
The client does. The platform subscription is in the company’s name. The data can be exported at any time. Custom modules, connectors and scripts are handed over with source code and documentation, and configuration notes are included so another team could take over.
How do you keep our customer and financial data safe during migration?
A signed NDA covers confidentiality before discovery begins. Migration uses restricted extracts, with access limited to the engineers on the project, and test environments use masked or limited data where practical. Credentials are rotated at handover. Permissions in the new system limit staff to the records their role requires.
What do you need from our side?
Three things. First, access to the people who run each process, for discovery interviews. Second, a named owner for each data set who can confirm which records and balances are correct, so that nobody guesses at a disputed figure. Third, one decision-maker. That person approves the platform choice and signs off each phase. Sample quotations, invoices, stock registers and salary sheets help more than a written specification.
Do we actually need an ERP or CRM, or can we keep running on your accounting software and Excel?
It depends on coordination, not company size. If your accounting software and a few well-kept spreadsheets give accurate numbers and nobody chases information between departments, no change may be needed, and that is stated during the assessment. Signs that a platform may help are sales, stock and accounts tracked in different places and hours spent each week on reconciliation. Others are customer details known to one department only.
Read before you decide.
Practical notes on the questions this service raises, not product marketing.
Why Employees Continue Using Excel After ERP Implementation
Why employees keep a shadow spreadsheet running after an ERP go-live, and how to tell a real software gap from a trust or training problem.
ERP vs CRM: What Is the Difference?
ERP runs internal operations such as stock and accounts, while CRM runs sales and customers. How they differ, where they overlap and which to adopt first.
Does Your Small Business Really Need an ERP?
How to tell whether cross-department coordination failures justify an ERP, or whether a smaller fix to one broken tool would do for now.
Signs That Your Business Needs a CRM
Checkable signs that your sales process has outgrown notebooks and WhatsApp, plus what a CRM fixes and what it leaves untouched.
Let’s Build the Right Software for Your Business
Tell us about your current operational challenge, spreadsheet bottleneck, or software requirement. An experienced engineer will review your workflow and reply within one business day.
- No obligation consultation
- Senior engineer reviews your brief
- Your operational details stay 100% confidential
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirementsRelated Practices & Services
API & System Integration
Connect your new platform to your accounting software, WhatsApp, payment gateways, your website and in-house applications through integrations that are maintained and secured. Nothing is left to manual export.
Business Process Automation
Automate the approvals, reminders and handoffs that sit around your business software. Work moves without someone chasing it through phone calls and chat groups.
Data Engineering & Business Intelligence
Turn the data now sitting in your ERP and CRM into consolidated reporting and management dashboards that read across systems, so one report answers what three used to.
Software Maintenance, Support & Rescue
Ongoing support, fixes and improvements for the systems you depend on, including projects left incomplete by a previous vendor and platforms that need a second look.