Home > Articles

Customizing an ERP During Implementation? Just Say No

Inevitably, your ERP implementation efforts will result in requests for customization of the system, either to make it operate more like the system(s) it is replacing or to enable an existing business process. Both scenarios should be expected—and resisted. In this article, Ajay Gupta presents a rationale for avoiding all customizations to ERP systems in their early stages, and at best postponing such customization decisions until later in the ERP's life cycle.
Like this article? We recommend

When you are implementing an Enterprise Resource Planning (ERP) system, you or your stakeholders will likely identify a number of areas where the new system may not perform in a manner consistent with the legacy system running the organization’s administrative business functions.  This is to be expected as no two ERP systems function the same. In particular, no ERP functions like either a Mainframe system or disjointed and disparate administrative software, which are the environments ERP systems often replace.  A common approach to dealing with such perceived shortcomings is to seek a customization of the new ERP, often in an attempt to make it function like the system it is replacing or to meet the organization’s existing operating practices.  While there can be gains in terms of user convenience for such efforts, customization is both expensive in the short term and presents a management, maintenance, and software version control burden in the long term.

In this article, I present a rationale for avoiding all customizations to ERP systems in their early stages and at best postponing such customization decisions until later in the ERP's life cycle.

NOTE: For convenience, I refer to ERP systems in this article; however, the rationale applies equally to Integrated Library Systems (ILS), Electronic Medical Record (EMR) systems, and other  administrative business software systems used throughout an organization.

The Rationale Against Customization During the Early Stage of ERP Implementation and Adoption

This section presents my general rationale for avoiding customizing an ERP and especially during early stages in its implementation.  It is my recommendation that organizations delay any and all customization for a minimum of six months, and preferably a full fiscal year, after the go-live date to allow staff a complete business cycle to use the ERP in a full production capability.  My specific reasons for discouraging customization during ERP implementation include the folllowing:

1. Customization Goes Against the Business Process Re-engineering Value of ERP Implementations

Enterprise resource planning systems can bring value to an organization in terms of its automation, defined internal workflow capabilities and—through increased decision support—transparency and operational efficiency.  However, to achieve these goals, organizations almost universally must commit to reassess and re-engineer their existing business processes.  

A pre-implementation stage is the ideal time to document current operations in an effort to find and cut out unnecessary steps, streamline operations and  reduce operating costs, as well as track how operations will translate into the new environment.  The exercise of examining business practices helps and is often considered critical to a successful migration to the new system.  However, this preliminary planning doesn't always happen, at least not as effectively as would be hoped.  

Another way an organization can ensure business processes are modified is to essentially force itself to operate with the new ERP right “out-of-the-box” and with no customizations, however slight, to the code, work flows, and system operations permitted in the first fiscal cycle.

Such a delay or postponement of customization efforts will be seen as a polite way to deny such requests.  Honestly, there may be some truth to this as postponing a request can be easier than openly saying no.  However, organizations that truly embrace the notion that the ERP implementation is an effort to change business practices that perhaps don't work as well as they did in the past, even though they have been done that way since forever, generally can find greater success in the overall project.

2. Cost

Given the current fiscal situation throughout our economy, avoiding measures that increase operating costs in both the short and long term is often essential.  At the least, such measures should be undertaken only when there is certainty about the fiscal budgets for the duration of the implementation project, and when there is certainty on the cost implications of the customization.

The true cost of customizing an ERP is rarely accurately considered and includes at a minimum all of the following:

  • Cost of custom code development by ERP vendor or 3rd party

    This is often the only factor considered.  However, what is considered is only the invoice amount presented on a custom code development proposal.  Cost overruns, mid-stream changes to scope, or modifications that account for insufficient requirements are not considered, even though many acknowledge such a likelihood.   

  • Additional end user training and consulting costs towards adoption of customized code

    Customizations, whether altering the core source code or creating a new workflow, are often funded through the original implementation budget and often at the expense of training and consulting dollars.  Introducing customized and unique code into an ERP system complicates the overall system use and management effort and usually requires additional training and consulting assistance.

    Its an interesting act of irony that training and consulting funds are often raided to fund the customizations in the first place, when the customization itself usually requires additional training and consulting support beyond what was originally allocated.   

    Further, since the ERP is customized, the ERP vendor's trainers and consulting professionals may themselves need time to learn how it now operates before they can effectively provide the training and consulting services.  Depending on the contract language for implementation support and consulting services, firms may have to pay for the time vendor representatives spend to learn the customization.

  • Increased cost of post-implementation ERP maintenance

    Changes made to an ERP often alter the work process when implementing a vendor's regular patch updates.  For example, many ERP systems present a social security number on screens that also provide other, less sensitive demographic information.  Given the concerns surrounding identity theft, many consider enacting measures to remove the SSN for such screens so the screen itself can still be assigned to users as necessary for the execution of their duties without giving those users access to the SSN.  It sounds worthwhile, and perhaps a change that removes one field from one screen will not be so expensive.  However, such a change will have to be tested each time a patch to the ERP system is made to ensure the new patches do not overlay, reverse or otherwise alter the coding changes made in the customization.  This added staff burden must be taken into consideration when evaluating this approach to making changes. 

    In light of this, the cost of customization should include the cost of custom code development, additional training and consulting expense, and additional manpower required to maintain the system in the long run.

    Further, customization necessarily involves time, which may push back go-live dates. If doing so involves financial penalties for missing delivery dates, such financial penalties should also be considered.

3. ERP Implementation and Adoption Considerations

Prior to actual “real world experience” in using an ERP to accomplish the numerous tasks that must be performed at all stages of the business cycle, staff may simply not be in the position to identify and articulate all of the areas where customization may present value. 

Until the organization has seen how the ERP supports all of its administrative and business functions—and certain functions only come up once or at certain stages in a fiscal year cycle—it may not be in position to know where enhancements will be most helpful to the organization.

Further, customizations have the potential to alter the ERP system in ways that affect its functionality in other areas.  As ERP systems are integrated systems, changes in one area can have unexpected and unintended consequences in other areas.  Often, these changes may not become apparent until later in the business cycle.  Only after a complete business cycle would the organization know how to articulate the design constraints that will affect the specific changes desired without compromising functionality in other areas.  

For example, a client implemented a customization to synchronize a Microsoft Active Directory with another, previously in-place LDAP directory in order to facilitate seamless new account creation.   However, upon doing so, users who changed their demographic and other account information in systems and applications attached to the LDAP directory were now changing their account information through to AD and to all applications leveraging that directory as well.  This led to users unintentionally locking themselves out of certain applications because their account information was now wrong. There were  also numerous cases of the unexpected release of sensitive demographic information.

While the synchronization between these two directories and efforts to simplify new account creation would certainly be considered beneficial, the customization effort turned out to be a net negative considering its costs, the inconvenience it brought to users and the loss of data confidentiality.

While functional user and technical staff are still trying to fully understand the operation of the ERP, they may not be in a position to fully articulate the design requirements for any customization, nor accurately predict the consequences of customizations they do implement, as the example above illustrates.

During the migration to the ERP, the first task is really to understand the ERP and its unique intricacies.  Customizing it at this early stage has the effect of giving both end users and technical staff a “moving target,” making such projects more challenging from both the operational and system administration perspective. 


In short, organizations should avoid a “rush to customize.”  It is to be expected that any new ERP system will have shortcomings, both real and perceived.  All work-arounds and alternatives should be explored before making a commitment to changing a system that is not yet fully implemented.  It is important to bear in mind that customization does not mean “fixing” an ERP, and there is no guarantee that the ERP will behave exactly as desired once a customization has been completed. There are numerous examples where programs were modified to address an expressed need only to discover the modified programs didn't achieve the desired result.   Customization in year two, or after the organization has reached maturity with the ERP, have a far greater change or being successful.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020