Dynamics 365 (D365) CRM and Business Central Partner in Armenia: CRM Consulting, ERP and the Power Platform from Senior Consultants and Developers in Yerevan

Check seven things. Who built and maintains the Armenian localization, and whether it runs as AL extensions on the international (W1) version of Business Central. Whether the partner can show VAT returns, statutory statements and State Revenue Committee e-invoicing working in a test company on your own data. Whether the same team does the 1C migration. Whether CRM and ERP sit in one team. Whether delivery runs in Armenian and Russian in your time zone. Who actually does the work. And who owns the AL source. Solzet builds the Business Central Armenian localization itself as extensions on W1, migrates from 1C, and designs the CRM, the ERP and the integration between them from Yerevan.

No. Microsoft makes Business Central online available in Armenia on the international (W1) base app and states that the localization for Armenia is provided by partners. Solzet builds and maintains the Business Central Armenian localization as AL extensions on W1: AMD as the local currency, an Armenian chart of accounts, Armenian tax and statutory reporting, Armenian-language documents, and State Revenue Committee e-invoicing where applicable. Payroll is not part of what the localization covers.

CRM consulting is the work of turning a business problem into a customer system people actually use, and it covers both the advice and the build. In practice that means auditing how an organization wins and keeps customers today, agreeing what the system has to do and what it should deliberately not try to do, designing the data model and the processes on top of it, implementing and customizing the platform, migrating the data that already exists, training the people who will work in it every day, and then supporting and extending it as the business changes. Buying the licences is not the project. Solzet does the consulting and the build on Microsoft Dynamics 365 Customer Engagement and the Power Platform, with Business Central and Finance and Operations on the ERP side, delivered from Yerevan, Armenia, for clients in Armenia and the Caucasus and for companies and Microsoft partners in Europe and the US.

Two jobs that are usually sold as one and often staffed as two. The advisory half is requirements, process design, the Dataverse data model, the phasing of releases, and the honest calls about where standard configuration is enough and where custom code is genuinely warranted. The delivery half is configuring the apps, writing the plug-ins, custom API, and PowerApps Component Framework (PCF) controls that configuration cannot express, building the integrations, running the release pipeline, and fixing what user acceptance testing finds. On a Solzet engagement the same senior, Microsoft-certified engineer does both, so the context gathered in discovery is not lost at a handover and paid for a second time later.

Ask four questions and judge the answers rather than the capability deck. Who will actually be on the project, at what seniority, with what certifications, and did those same people do the scoping. What time zone do the engineers sit in, as opposed to where the head office is registered, and how many hours a day overlap with yours. What happens when it goes wrong: do they take over work another supplier started, and is project rescue a named service with published scope or a favour they would attempt. And how is it priced: whether licences and implementation are separated in the quote, and whether the basis is time and materials or fixed price per milestone. Apply all four to us as well. Our certifications, engagement models, case studies, and delivery facts are published on this site rather than described on a call.

Yes, and most of our delivery is cross-border. Yerevan is our only hub, and from it we deliver CRM consulting to organizations across Armenia and the wider Caucasus region and to companies and Microsoft partners in Europe and the US. The model is the same either way: senior, Microsoft-certified engineers working remotely over Teams or Zoom, inside your Azure DevOps, GitHub, or Jira, on B2B contracts with NDA and a GDPR-compliant DPA, invoiced in EUR, USD, or GBP by wire transfer. GMT+4 leaves roughly 4 to 6 hours of daily live overlap with Western Europe and 6 to 8 with the UK, which is enough for standups, workshops, demos, and a decision inside the same day.

The whole path from the decision to a running system, and with Solzet it is one Yerevan team throughout. Discovery: an audit of how you win and keep customers today, the requirements that follow from it, and a phased scope you can actually fund. Implementation on Dynamics 365 Customer Engagement: the Dataverse data model, forms and views, business process flows, security roles, dashboards, and the automation that replaces manual steps. Customization and custom development where standard configuration runs out: plug-ins, custom API, PowerApps Component Framework (PCF) controls, and Power Automate. Migration: accounts, contacts, and history out of spreadsheets or an older CRM. Adoption: training, hypercare, and the improvements that real usage exposes. Microsoft licences are bought separately, per user per month, at list prices that are the same anywhere in the world. The consulting and the build are the part a partner delivers.

A first conversation with the senior engineers who would actually do the work rather than with a sales layer, at no cost. You describe the situation, whether that is a first CRM replacing spreadsheets, a legacy system nobody can extend, a move from another CRM platform, or an implementation that has stalled, and we tell you what we think it needs, what it does not need, and roughly what a sensible first phase looks like. If there is a fit we propose a free two-week discovery sprint with no obligation: we assess your environment, document the requirements, and deliver a solution proposal that is yours whether or not you continue with us. From there you choose the commercial basis, time and materials or fixed price per milestone. We reply within one business day, and the whole thing runs in English, Armenian, or Russian.

Yes, and in our case the two job titles describe the same role: CRM developer is the platform neutral title and our platform is Microsoft Dynamics 365 Customer Engagement on Dataverse. Our developers are senior, Microsoft-certified, and based in Yerevan in GMT+4, and they work inside your Azure DevOps, GitHub, or Jira and to your branching and review rules rather than running a separate process on the side. You can engage them as a dedicated developer or small team inside your own project, for a fixed scope build, for managed support on an environment that already exists, or white-label behind another Microsoft partner. Our Dynamics 365 and CRM developer service page sets out the engagement models in detail.

Four things, in practice. The Dataverse layer: tables, relationships, alternate keys, business rules, security roles, and column level security, designed once rather than reworked after user acceptance testing. Server side logic: plug-ins and custom API on the Dataverse event pipeline for pricing, discount, validation, and approval rules that must run whether the record comes from a form, an integration, or a bulk import. Interface: PCF controls in TypeScript and React where a standard control cannot express what users need, which is the work other Microsoft partners most often subcontract to us. Integration: the Dataverse Web API, custom connectors, and Power Automate, with authentication, field mapping, retries, and error handling that surfaces a failure instead of hiding it. Around all four sits managed solution and release management, which is what keeps the build cheap to change later.

Yes. Solzet is a Dynamics 365 consultancy headquartered in Yerevan, Armenia. We implement Microsoft Dynamics 365 Customer Engagement, and for organizations that need CRM without Microsoft licensing we build custom CRM systems on React, Node.js, PostgreSQL, and .NET. That covers Dynamics 365 Sales for pipeline and account management, Customer Service for cases and SLAs, Field Service for scheduling and mobile engineers, and Customer Insights for marketing journeys, all on the Dataverse data model. We implement it for organizations in Armenia and across the Caucasus region, and for clients and Microsoft partners in Europe and the US, from one Yerevan team of senior, Microsoft-certified engineers. When the CRM needs an ERP beside it, we also implement Business Central, including the Business Central Armenian localization, and Finance and Operations.

Solzet does, from Yerevan. We are a Microsoft partner specializing in Dynamics 365 Customer Engagement, the Microsoft CRM, and the Power Platform, and CRM implementation in Armenia and the Caucasus region is a core part of what we do, for Armenian enterprises, government and public sector bodies, and alongside our work for clients and Microsoft partners in Europe and the US. The people who scope your CRM are the senior, Microsoft-certified engineers who then configure, develop, and support it: there is no offshore back office behind us and no account layer in between. We also build custom CRMs for organizations that cannot or will not adopt Microsoft licensing, so we recommend the right solution rather than the one we happen to sell. On the ERP side we implement Business Central, with the Business Central Armenian localization, and Finance and Operations.

It depends on scope, but the published evidence gives a realistic range. Our four case studies ran three to five months each with teams of two to three senior consultants, covering a bank CRM replacement with more than 200,000 migrated records, a field service rollout for 50 plus technicians, a Dynamics 365 Sales and Power Apps build for an 80 plus consultant firm, and eight custom PCF controls for a UK Microsoft partner. A mid-market CRM build in Armenia usually sits in that same band. A tightly scoped first phase covering one team and one process can go live sooner, with further apps and integrations added in stages rather than in a single cutover.

Dynamics 365 and Dataverse run in Microsoft datacentres, and the region is chosen when the environment is created rather than adjusted later. There is no Microsoft datacentre in Armenia, so organizations here normally run in a European region, which also keeps a GDPR-compliant DPA straightforward for anyone trading into the EU. We advise on the choice before the environment is set up, because changing it afterwards is a support-led migration rather than a setting you flip. Your data stays yours throughout, and IP ownership is defined in the SOW before work starts.

Yes. Our working languages are English, Armenian, and Russian, so workshops, training, and support for a team in Armenia or elsewhere in the Caucasus can run in the language your people actually use, while documentation and code stay in English for anyone who inherits the system later. Dynamics 365 itself ships with a large set of interface languages that can be enabled per user, Russian among them, and any labels, forms, and views we build can be configured to match how your team refers to things rather than to a generic template.

D365 is the common shorthand for Microsoft Dynamics 365, the Microsoft family of business applications. There is no difference between the two names: consultants, recruiters, and project teams write D365 because it is shorter, and Microsoft writes Dynamics 365 in its own documentation. Within D365 there are two halves. The CRM half is Dynamics 365 Customer Engagement, made up of D365 Sales, Customer Service, Field Service, and Customer Insights on the shared Dataverse data model. The other half is ERP: Dynamics 365 Business Central and Finance and Operations, and Solzet implements both. One team can therefore design the CRM, the ERP and the integration between them.

Yes. Solzet is headquartered in Yerevan and D365 is what we do: implementing and configuring D365 Sales, Customer Service, Field Service, and Customer Insights on Dataverse, migrating data off spreadsheets or a legacy system, building Power Apps and Power Automate solutions around them, developing plug-ins and custom PowerApps Component Framework (PCF) controls, rescuing D365 projects that have stalled, and supporting the system after go live. We deliver that for organizations in Armenia and across the Caucasus region, and for clients and Microsoft partners in Europe and the US, from one Yerevan team of senior, Microsoft-certified engineers holding PL-200, PL-400, PL-600, MB-210, MB-230, and MB-240. On the ERP side of D365 we implement Business Central, with the Business Central Armenian localization, and Finance and Operations.

Dynamics 365 Customer Engagement is Microsoft CRM. The name changed over the years, from Microsoft Dynamics CRM to Dynamics 365, and the product was split into apps (Sales, Customer Service, Field Service, Customer Insights) that sit on a shared Dataverse database, but the job is the same job a CRM has always done: one trusted record of your customers, your pipeline, and every interaction with them. The other half of the Dynamics 365 range is ERP rather than CRM: Business Central and Finance and Operations, which Solzet implements as well, so one team can design the CRM, the ERP and the integration between them. Custom-built CRM remains the option for clients who need one without Microsoft licensing.

We recommend the right solution: Dynamics 365 (Customer Engagement, Business Central or Finance and Operations), Power Platform, or a custom-built CRM, and for the CRM itself it depends on where you are starting from. A small team tracking a short customer list is often fine in spreadsheets for a while. A sales team that needs a pipeline and nothing more is well served by a standalone SaaS CRM such as Salesforce, HubSpot, or Zoho. Dynamics 365 Customer Engagement is the stronger choice when you already run Microsoft 365 and Teams, when sales, service, and field operations need to share one customer record, or when the system has to be genuinely customized and integrated rather than configured from a menu. A custom-built CRM is the better choice when Microsoft licensing is beyond the budget, when you need full ownership of the code and hosting, or when your process is too specific for a packaged product, provided it is engineered and supported by a team. What we would argue against in every case is a system, packaged or custom, that only one developer understands, because that is the thing our clients most often ask us to replace.

Yes, and it is one of our most common projects. We migrate from spreadsheets, from on-premises or bespoke systems, from older Dynamics CRM versions, and from other CRM platforms including Salesforce, HubSpot, and Zoho. The work is the same shape each time: map the existing entities and relationships onto the Dataverse model, agree what history is actually worth bringing across, build and test the data migration, rebuild business logic as plug-ins and Power Automate flows, rebuild custom screens as PCF controls where they are needed, then cut over in stages rather than all at once. Our published European bank engagement replaced a 15-year-old on-premises CRM and migrated more than 200,000 historical records this way.

Six kinds of supplier serve this market, and knowing which kind you are talking to matters more than the name on the door. Yerevan based Dynamics 365 and Power Platform specialists, of which Solzet is one, are specialist firms whose whole practice is Microsoft business applications. Armenian and regional IT services companies run a Microsoft team alongside web, mobile, and QA work. International partners in Western Europe, the UK, or the Gulf sell into the region without an office in it. Global systems integrators run multi-country programs from abroad. Independent contractors and marketplace freelancers work solo. Licensing resellers sell Microsoft licences and often subcontract the build. We do not publish a ranked list of named competitors, because we cannot verify another firm on team seniority, response times, or rescue record, and a list that conveniently ended with us would not be worth reading. The partner directory on this page sets out all six categories against delivery style, regional expertise, and crisis response so you can place any firm you find.

There is. The Microsoft Solution Partner directory and AppSource will confirm that a company exists, where it is registered, and that it holds a partner agreement, and it is worth checking for any supplier you shortlist. What it will not tell you is the part that decides your project: who would actually be on it and at what seniority, what time zone those engineers sit in as opposed to where the head office is, whether the people who scope the work are the people who build it, and whether the firm takes over an implementation somebody else started. Those are the three axes the directory on this page is organized around instead. Use both: Microsoft to confirm a company is real, the categories and shortlist questions here to work out what you would actually be buying.

Start by ruling out the categories that cannot help at short notice. A global integrator will treat it as a new engagement with its own procurement cycle. A generalist IT services company can only help if a certified Dynamics 365 engineer happens to be free that week. A reseller will route you onward. A lone freelancer can start tomorrow but is a single point of failure halfway through. What you want is a specialist team small enough to put senior people on it immediately and experienced enough to have done it before, and the question to ask is whether project rescue is a named service with published scope rather than something they would attempt as a favour. For Solzet it is a named service: our project rescue and takeover page covers a stalled implementation, a build abandoned by a previous partner, a migration that halted before cutover, and a live system failing in production, and the health check and technical audit is the fixed scope diagnosis to run first if you do not yet know how bad it is.

Yes. Yerevan is our only delivery hub and we deliver Dynamics 365 Customer Engagement and Power Platform work remotely across the Caucasus region and its neighbouring markets from it, on the same model we use for clients in Europe and the US: senior certified engineers, remote delivery, and a time zone that overlaps yours. For a client elsewhere in the Caucasus the working day is effectively identical to ours, which is the practical advantage over a partner running the build from Western Europe. Contracting is straightforward, since Solzet is registered in Armenia and works on B2B contracts with NDA and a GDPR-compliant DPA and invoicing in EUR, USD, or GBP by wire transfer, so a cross-border engagement is a normal one for us rather than an exception.

With owner-based security and hierarchy security rather than new business units. Each client is owned by its rep, and the sales role grants User-level read and write on accounts, contacts, leads and opportunities, so reps see what they own. Hierarchy security on the manager hierarchy, with the Manager field filled in on every user and the client tables included, lets a direct manager read and edit records owned by their reports and higher managers read them. The head of sales gets a role with Organization-level read. Owner teams hold shared pools, and business units are added only when branches or legal entities must not see each other. Our guide to the Dynamics 365 security model covers the full design rule and the change order.

Yes, if the change is sequenced. We record what each persona can see first, copy the existing role rather than editing it in place, rehearse the change in a sandbox copy of production, add the new access before removing the old, check the application users that integrations and Power Automate flows run under, and retest with real users after every step. Moving a user to another business unit removes their security roles by default, which is the most common way visibility gets lost, so business unit moves are planned and logged rather than made ad hoc. Hierarchy and modernized business unit settings vary by environment, so we check them against current Microsoft documentation before the first change.

Да. Мы работаем на русском, армянском и английском языках: встречи, обучение и поддержка проходят на языке ваших сотрудников, а документация и код остаются на английском, чтобы систему мог поддерживать любой специалист. Проекты, начатые другим подрядчиком, мы берём на себя после технического аудита: проверяем настройки, плагины, потоки, данные и модель безопасности, говорим прямо, что стоит сохранить, а что переделать, и только потом продолжаем работу. Чаще всего первая задача - настроить доступ так, чтобы менеджеры видели только своих клиентов, а руководитель видел всех.

Yes. Solzet is a Microsoft Dynamics 365 and Power Platform consultancy headquartered in Yerevan, Armenia, delivering CRM, ERP and integration projects for Armenian companies, government and international clients. We act as a local Dynamics 365 partner for organizations across Armenia and the Caucasus region, and we also deliver to clients and Microsoft partners in Europe and the US. Our engineers hold Microsoft certifications including PL-200, PL-400, and PL-600 for the Power Platform and MB-210, MB-230, and MB-240 for Dynamics 365 Customer Engagement.

Solzet is a Microsoft Dynamics 365 and Power Platform consultancy registered in Armenia, founded in 2024 and headquartered at Hakob Hakobyan 1, Yerevan, Armenia, in the GMT+4 time zone. Its senior consultants and full-stack developers bring 8+ years of CRM delivery experience, with delivery capacity expanded per project. It delivers Dynamics 365 Customer Engagement (Sales, Customer Service, Field Service, Customer Insights), the Power Platform (Power Apps, Power Pages, Power Automate, Copilot Studio, Dataverse), PCF controls, project rescue, white-label subcontracting for Microsoft partners, and custom CRM on React, Node.js, PostgreSQL and .NET. Working languages are English, Armenian and Russian, and the contact address is contact@solzet.com. The company profile, the Yerevan experts guide and the published case studies carry the detail.

Either. A direct engagement is a B2B contract with Solzet, with an NDA and a GDPR-compliant DPA, invoiced in EUR, GBP or USD by wire transfer, on time and materials or fixed price per milestone, with IP ownership defined in the SOW. If you already work with a Microsoft partner, they can hold the contract and the relationship while we deliver white-label behind their brand, in their tooling. Either way your Microsoft licences stay in your own name, so the implementation partner can change without touching the subscription.

The data lives in Microsoft datacentres in the region chosen when each Dataverse environment is created, and geographies include the United Kingdom, Germany and Europe, so the choice follows your requirement rather than our location. We confirm the region with you before any environment is set up, because moving it later is a support-led migration. We work inside your own Microsoft tenant, with accounts and security roles you control, and your CRM data is not copied into a Solzet tenant. Remote access by our engineers from Yerevan, outside the EU and UK, is covered by the GDPR-compliant DPA, and generative AI features that can process data outside your geography are reviewed with you before they are switched on.

For clients in the UK, the Netherlands, Germany and the US, delivery is remote: workshops, standups and demos over Teams or Zoom, in your Azure DevOps, GitHub or Jira, within the daily overlap GMT+4 gives with European hours. On-site delivery is in Yerevan, for Armenian enterprises, government bodies and regional clients when being in the room changes the outcome. We do not advertise a standing presence in Western Europe, so if an in-person session at your office matters for a milestone, raise it during scoping and it is agreed in the SOW rather than assumed.

Yes. Solzet implements Dynamics 365 Business Central and Finance and Operations, alongside Customer Engagement and Power Platform. We handle implementation, extensions in AL and X++, migrations from Dynamics NAV, Dynamics GP, Dynamics AX and 1C, the Business Central Armenian localization, and the integration between your CRM and ERP. If you want one supplier for CRM and ERP under a single contract, that is the arrangement we prefer: one team for the CRM, the ERP and the integration between them.

Yes. Solzet delivers the Business Central Armenian localization: AMD as the local currency, Armenian tax and statutory reporting, an Armenian chart of accounts, Armenian-language documents, and e-invoicing integration with the State Revenue Committee where applicable. Solzet builds it as extensions on the international (W1) version of Dynamics 365 Business Central, which is available in Armenia.

Both halves of the range. On the CRM side, Dynamics 365 Customer Engagement, which covers D365 Sales, D365 Customer Service, D365 Field Service, and D365 Customer Insights (the app that replaced Dynamics 365 Marketing), together with the wider Power Platform (Power Apps, Power Automate, and Dataverse) and custom development such as plug-ins and PowerApps Component Framework (PCF) controls. On the ERP side, Dynamics 365 Business Central, including the Business Central Armenian localization, and Finance and Operations (Dynamics 365 Finance, Supply Chain Management, Commerce and Project Operations), extended in AL and X++. For clients who need CRM without Microsoft licensing, we also build a custom CRM.

Yes. While we are a local partner for Armenia and the Caucasus region, most of our delivery is international. We work with mid-market companies and Microsoft partners across Europe and the US. Armenia sits in the GMT+4 time zone, which leaves several hours of daily overlap with European and UK business hours for standups, workshops, and reviews over Teams or Zoom.

Because the work is done by senior, certified engineers rather than passed down a chain, in a working day that overlaps yours. You get genuine technical depth in Dynamics 365 Customer Engagement, the Power Platform, and custom development, from a team that stays with your project from scoping through to support.

On three things. Access: there is no sales or account management layer, so you work with the engineers who build your system from the first call. Time zone: we work in GMT+4, the same working day as Armenia and the Caucasus region, with roughly 4 to 6 hours of daily live overlap with Western Europe and 6 to 8 with the UK, rather than the overnight cycle of a distant offshore delivery centre. Team: large-scale partners staff a pyramid, with senior architects on the pitch and juniors on the build, while every Solzet CRM engagement is staffed with Microsoft-certified senior engineers, typically a team of two to three. Where a large integrator does win is multi-country programs with heavy governance needs.

By removing the structural causes rather than promising harder. Time zone: Yerevan is GMT+4, so there is live overlap with your working day every day instead of an overnight cycle. Team: engagements are staffed with senior, Microsoft-certified engineers who scope, build, and then support the same system, so there is no handover from the people who sold it to a bench of juniors, and no rotation onto another account mid project. Visibility: we work in your Azure DevOps, GitHub, or Jira and in your Dataverse environments, with a working demo at the end of each iteration rather than a status report. Exit: you own the source, the solutions, and written handover documentation, with IP ownership defined in the SOW before work starts. Commercially it is a normal B2B contract with NDA and a GDPR-compliant DPA, invoiced in EUR, USD, or GBP.

Yes. Dynamics 365 Customer Engagement and the Power Platform are one practice for us, not two. From Yerevan we build canvas and model-driven Power Apps, Power Automate cloud and desktop flows, Power Pages portals, and Dataverse solutions, plus custom PowerApps Component Framework (PCF) controls in TypeScript and React. That work can sit on top of a Dynamics 365 implementation or stand on its own, and it reaches Business Central and Finance and Operations data through virtual tables. The Power Platform development and support in Armenia page covers that side in detail.

We publish four engagements in full, covering a European bank CRM modernization, field service digitization for a European manufacturer, CRM and project tracking for a management consultancy, and eight custom PCF controls delivered white-label for a UK Microsoft partner. All were delivered from the Yerevan hub by teams of two to three senior consultants over three to five months. We do not publish named Armenian or Caucasus client stories, because our engagements run under mutual NDA and a share of our work is white-label behind other Microsoft partners. If you want a reference relevant to your own Dynamics 365 app, ask for one during the scoping conversation.

Yes. Alongside our direct client work, we provide Dynamics 365 Customer Engagement and Power Platform capacity on a white-label, B2B basis for other Microsoft partners. You keep the client relationship and your brand, and our certified Customer Engagement and Power Platform engineers work behind it, including custom development and PCF controls, on time zones that overlap with your working day. Business Central (AL) and Finance and Operations (X++) capacity is available on the same white-label terms, delivered by Solzet.

Solzet is headquartered in Yerevan, Armenia, and the implementation is done by that Yerevan team. There is no offshore back office behind us and no account layer between you and the engineers: the people who scope your Dynamics 365 project are the people who configure, develop, and support it. We work in the GMT+4 time zone, in English, Armenian, and Russian, on B2B contracts, using your own Azure DevOps, GitHub, or Jira and meeting over Teams or Zoom.

We do not publish fixed prices, because a CRM implementation on Dynamics 365 Customer Engagement depends entirely on scope: how many users and apps, how much of the process is standard configuration versus custom development, and how much data has to be migrated. Two things are worth separating in your budget. Microsoft licences are bought per user per month from Microsoft at published list prices, the same anywhere in the world. The implementation is what varies, and every day of it is senior, certified engineering. We quote on time and materials or fixed price per milestone after a scoping conversation, so you see the basis before you commit.

Yes. Project rescue and takeover is one of our core services. If a Dynamics 365 implementation has stalled, overrun, or lost its previous partner, we can step in to stabilize it, diagnose what is really wrong, and get delivery back on track, whether that means taking over a build in progress or fixing a live system that is not performing as it should.