The deployment of SuccessFactors is easy, though it can take from three to six months. There are a lot of different modules that each deployment requires, but luckily there are many common features that you can use across different deployments.

At the end of the day, a lot of things happen on the config within production, and I don't like that. We're going to push now to actually have and follow the three-tier. You can do that in a certain space, and then you go to production. My manager that I'm reporting to is going to make a few plans, and we're going to have a stage integration because integration is done too late in production since, after that, one sits with lots of data in there, along with issues, errors and with things stopping. SAP is also going against the own development methodology of their three-tier, which involves one to develop, realize, and deploy. Fundamentally, clients now have to pay for the stage, and that shouldn't be like that. If one moves from an on-prem tool, SuccessFactors should give that person exactly the like-for-like. And as I say, the like for like, it means from the architecture, they should give one development. They should also give that person the stage, along with the provisioning. In short, one shouldn't pay for the stage. Because once the things are in production, it's too late. After that, where do you do testing? In development? How can one do testing in development? So, now one has to configure in the config causing SAP's golden client, as we call it, to not go through configuration anymore. It's now changed. I think that is something SAP has to look at in the future.

Implementing SuccessFactors has been easy for me, but this is more of a general trend. 

The tool's deployment is complex due to various dependencies. The steps included user training, documentation, configuration, and aligning training for end-users. Around 25-30 resources were involved in the deployment. The overall deployment rollout takes two days to complete. If it is a complex project, it can take around four days. 

The initial setup of this solution is hybrid. I don't know if it's complex because I'm not a technical person to judge, but I can tell it's hybrid. We have a cloud solution which is SuccessFactors, and we have an on-premise payroll.

SAP has an integration module called HCI that IBM helped build between these two separate solutions, one being on cloud and one being on-premises.

The solution was deployed over a period of six months.

From a user's perspective, setting up the account was easy. We received the credentials when I joined the organization. We only had to fill in the credentials and get started.

It's a good setup but with emerging solutions like Darwinbox, I think there might be challenges ahead because of the user experience and that will dominate things in the next few years. 

The initial setup is easy. The deployment takes two weeks. The product is deployed on the cloud. We use a public cloud provider.

The setup was straightforward. Also, SaaS has made a lot of things easier. I rate their implementations as eight out of ten. They have a powerful learning hub. I respect the way they clarify their system and explain their processes.

We are a large organization and implementation has been a massive project. All our resources went into it and it's been a very complex process. We're still having some teething issues that the team is working on. Not all the issues are connected to the solution but in the context of an organization operating in a highly regulated area, the financial industry, and in 60 countries, it's a complex organization. Any solution will be difficult to implement. We had external assistance for the implementation. 

Before we began the setup, we engaged in requirement gathering, brainstorming, kickoff meetings, and various other sessions that really gave us an edge when it came to the actual implementation. Prior to SuccessFactors, we already had other software in use and when we had to migrate everything over to SuccessFactors, we made sure that we were fully prepared.

Reflecting on the initial challenges we faced during the migration, I can advise that, without a doubt, the most important thing is to spend enough time gathering all your requirements and data before you jump in.

On the whole, I wouldn't say it was easy to implement. Because it was a matter of adding something completely new to the organization, it had its ups and downs, and I would lean toward calling the setup moderately difficult.

On a scale of one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight.

Presently, the solution is deployed on the cloud. The deployment process took over a span of three years. However, the initial setup process took only a few hours.

If the number of employees required for the deployment of the entire group is considered, then around 3000 employees were required to implement the solution. However, since I managed the implementation process in one country, only 170 employees were required to implement the solution.

The implementation of SAP SuccessFactors is highly complex.

We are a pharma company and in this domain, it's very important to have mandatory training. All the inside notes and email that has been sent to the employees are very heavy and it's not easy to modify them because it's part of the suite. It is very complex to use. It's not easy to change things and if you would like to change things, we need to wait six months. We can wait for a long time, and if there are not any other customers that need the changes we will not receive priority.

The initial implementation is done by SAP-certified SuccessFactors Consultants. It is not too complicated but it has to be done by trained and certified individuals. SAP has a vast ecosystem of support and there are many System Integrators and people available for the implementation, such as ourselves.

The tool's deployment took a couple of weeks to complete. 

The initial setup is not the easiest. I'd rate the ease of implementation a six or seven out of ten. It depends on the deployment. It might be easier if it is an SME that is deploying it. The more complex a company gets the more complex the setup. 

For the solution's initial setup, on a scale of one to ten, where one is difficult, and ten is easy, I rate this solution an eight.

The deployment process for SAP SuccessFactors Compensation took around five to six months.

Two people were majorly involved in the deployment process. People with the job roles of analyst, business analyst, and consultant were involved in the deployment process.

Generally speaking, setting up SuccessFactors is straightforward, but some clients have complicated requirements. The standard SAP configuration is easy for consultants because they have a rapid implementation tool to deploy the baseline solution, so a client can have the system running in days. It depends on the client's requirements, but it is much easier for the end user than the consultant.

The total deployment time also varies depending on the modules. Let's say, you want to implement Employee Central plus the performance assessment and recruiting modules. This might be tricky depending on the size of the organization. Implementing this solution for a large organization requires a lot of data work to gather employee information. If you have all the employee records in place, you can deploy the solution in three months. When you don't have the data, you need to gather it and create templates. It can take much longer to deploy.

The initial setup was quite complex, and implementation took a long time, about two years, because of the amount of customization we had to do.

The partners took care of the setup, so we haven't done many configurations on it. Only the partners are exclusively involved in the configuration and the development work.

There are a lot of modules and integrations that need to take place while implementing the solution. It is complex to implement. For example, it can be difficult to enable specific groups of users to access certain modules or features.

Once we have the payment from the customer we can deploy the solution in six to eight weeks. This includes all the necessary modules and configurations suitable to the customer's needs.

The initial implementation is SAP SuccessFactors straightforward. The full process of deployment took us six months.

Initial setup was not very complex. If you're looking at an ERP sort of a solution, there is complexity with the way you want to define your organization. If the organization is clear about that, in terms of business unit, division, function, departments, the way you want to structure your organization, then it is not a problem. But if that is not clear, then of course, it is an issue.

The initial setup is easy, however, we need to explain to the employee about the process of the performance system due to the fact that, for the most part, they don't know how much is processed in their performance management system. We'll give direction and then it's easy for them to handle. We'll also follow up to make sure they understand and everything makes sense. 

Setting up SAP SuccessFactors is easy, and it has zero downtime. It generally takes three months to deploy any talent module or employee central of SAP SuccessFactors.

The initial setup is complicated. 

The setup is a matter of planning. If you get your planning right, the deployment of SAP or any part of the module will look very easy. With the proper planning, you will have the right skills and the right SAP partner that can partner with you in the rollout, and you'll be able to deliver with little or no hitch.

I wasn't there during the setup, but I don't think the setup was complex because there were a few things we've implemented and implementation of those weren't complex.

The initial setup was very straightforward and hardly took any time - we were up within a few weeks.

The initial setup can be easy or hard, depending on how you go about it. If you go with the best practices, then you hardly need any setup. You simply adopt the existing processes and this is very easy and straightforward.

If you go without the best practices, such as when the company asks for new processes that are not included, or if you have to do a complex setup right from the beginning, then it will take some effort. But overall, the setup is still very easy.

It all starts with the data model, and obviously this requires someone experienced in Excel, etc., but once it is up and running, you will have screens that can be managed through the SuccessFactors' system without using any XML process. This makes things much more flexible in terms of setup compared to before. For any new processes you'd like to add, you can go directly to the upgrade center and select whichever optional upgrades you want. Thus, enhancing the software is very easy and doesn't take much time.

I was not involved in setting it up. I was involved with the data integrations, which were very complex. They have a set of web services and connections to them. The libraries were not up-to-date and this contributed to the complexity.

The initial setup is straightforward. For deployment, if we are going for just one module, it takes around three to four months.

The initial setup for SAP SuccessFactors was not straightforward, but it still depends on your implementation plan, and it's based on your business needs. To be specific, the setup isn't complex or straightforward. It's a combination of both. On a scale of one to five, I'm rating the initial setup for the solution a four. The deployment of SAP SuccessFactors took six months to complete.

The initial setup was straightforward. Deployment times will vary from country to country according to the numbers, but most companies can implement it within three to six months.

You need to have some technical people on your team with you. You need one or two just to hand you each module and to help you understand the standard process so you can deploy and not forget any important features. From the business side, you also need from one to two people to be available during the implementation just to ensure that the user acceptance testing is done very well. It's a good idea to have a consultant visit with your team during implementation to check what was implemented inside of the business processes. They will help you understand the limitation of the space.

I rate the product's installation a ten out of ten. It took six months to complete. We did the deployment according to the SAP activation process. We relied on 10 people to handle the deployment. 

The initial setup was easy. It is a user-friendly solution. 

The initial setup of SAP SuccessFactors is easy.

SAP SuccessFactors is simple to set up.

Every module in SAP SuccessFactors is complex in its own way. LMS and Time Management, in particular, require extensive configuration knowledge, experience, and hands-on experience. Only certified consultants are encouraged to apply.

If you have a large customer base with thousands of records to deploy, it could take three, four, or four to five months.

Maintenance is determined by the scope of the project. If it is a large company with more than 50,000 employees, 50 plus countries, and multiple locals, then at least four to five consultants are required because configuration changes, support, maintenance, and everything else will be required, and some of the aspects in SuccessFactors require extensive experience, hands-on, and knowledge.

We have had large-scale implementations of SAP SuccessFactors. The implementation is neither easy nor very difficult. If it's done right it can be easy and seamless but there's quite a lot of effort that is required. You need experts to do it.

The implementation lifecycle can be further reduced.

The initial setup of this solution is not complex at all. It is very easy. If we have any issues then we can ask technical support for an answer.

The length of time for deployment depends on the customer and their environment, but I expect that it takes four months at the maximum. For our client, the deployment took approximately three months, and four people were involved. One or two people are sufficient for maintenance.

The initial setup was straightforward. SAP was really supportive during this time.

I was not involved in the initial setup, however, my understanding is it was likely complex. 

The initial setup is somewhat complex. We get the software and it's in the cloud and they still said we'd have to do a lot of integration with our recorded on-premise systems for it. It's not that simple, it's quite complex. There is a lot of coordination involved in order to make it happen.

The ease, or complexity, of the initial setup is dependent on the expertise level of the implementation partners, who will need to be certified in at least one module being deployed.

There are standard test cases, test scripts, best practices, implementation metrics, phases, timelines, and the way the project is generally executed. As long as these are adhered to, then the implementation is straightforward, but it is not admin-friendly and cannot be carried out solely in-house.

From a technical perspective, the initial setup is straightforward because SAP is engaged in the implementation. But from the customer's point of view, it's a little challenging because it's a new platform, so it requires some training before it can be used. That means that while the roadmap of implementation is six to eight months, there is an additional four to five months of user training.

The initial setup is straightforward because there are templates and best practices. We can just click on the button from the online center, deploy it into the system, and it sets it up for us.

The time it takes to deploy depends on the requirements and it depends on the number of modes that you deploy. As long as you have clear requirements from the client, it can take between three and four months. It doesn’t take too much time to deploy as long as you have clear requirements.

The initial setup is not overly complex or difficult. We found it straightforward. It's simple to set up. A company shouldn't have any issues with the process.

The setup is straightforward and SAP provided adequate and updated version documents for reference.

Setup was straightforward, but that was only because our implementation team (IBM) did all of that for us and walked us through everything. Eventually, we realized how intuitive the process actually is.

There were a few consultants from SuccessFactors who came in and did the installation. They were helpful in setting up the product and doing the initial customization, after which we took over.

The initial setup is quite straight forward. It's not complex due to the fact that it deploys to the cloud.

For us, it was what they expected, and it was very straight forward. 

We have our own team that manages the solution in house. For Success Factors, generally, if we use the standard solution, and there are not too many customizations, then it requires maybe a maximum of five people to maintain everything. Generally, maybe more in the beginning, it may be a few more people. However, as the system stabilizes, it's probably five maximum. Five to ten people, maximum, are needed.  That's quite a large acknowledgement, I would say, if I'm honest.

We didn't have a good data set, so the personal master data was a mess. It was a lot of work, especially on the data side. After one or two years, we kind of fixed it. 

It took about nine months to roll it out. We rolled it out in parts because we are a company that is active in 38 countries, with 450,000 associates. On our site, we had around 5,000 associates at that time. Currently, we have 4,000 associates because we are shrinking. 

In terms of the implementation strategy, we are tech equipped company. It was designed without any negotiation or input from the end-user. It was a technology push if you want to see it like that.

The initial setup was straightforward. It's very easy on the cloud. 

I think the initial setup is straightforward, but they could give users some direction for setting it up for the first time. 

Initial setup was straightforward. We aligned business processes, where needed, to the SF solution.

The installation was straightforward initially, but also complex and vast while dealing with data migration and mapping. You need good knowledge of the product.

You need a good background when dealing with MDF objects. You also need the right configuration and an understanding of SAP on-premise for hybrid scenarios.

Initial setup was straightforward, as global and lean master data was maintained in the previous system.

Initial setup is very smooth; all processes are very well defined and documented.

Setup was really straightforward with a simple implementation road map and an open configuration that can be easily or mostly supported by local company admins.

The installation was a bit complex. They are more complicated than other cloud solutions.

SAP implementation is not an easy thing. SAP implementation is an issue.

Initial setup was straightforward; complexity lied within consolidating processes across the organisation and simplifying to ensure requirements could be met by best practices in the SuccessFactors solution.

Initial setup was straightforward.

If you do a good analysis, the setup is never hard. The most difficult thing is the analysis.

a. Employee Central is critical, you need to have a good experience to work on it. Is very powerful because the choices will impact also on the other modules. We are called to support some projects that were in fact blocked for wrong configurations due to limited product knowledge by other partners.

The initial setup was straightforward. It's not that complex.