Magento Migration

Support for Magento 1 has been terminated. If you want to keep your shop up-to-date and perfectly compatible with the new extensions then migration to Magento 2 is a necessity.

migration

Data migration is a key phase in the transfer process. To perform migration one must have sufficient technical knowledge and experience. Only they will aid you in case you need a quick reaction to the possibility of losing resources from the database, especially data about your clients and your products. What’s more, only practical knowledge will allow you to avoid errors and make you aware that all of the contents of your blog, metadata, and customers orders should be transferred indissociably.

For whom?

Key phases of Magento Migration

Phase 1

We start with the review of data and content of the WWW website to correctly estimate how much work needs to be done. Next, we prepare project specifications, create the project schedule with the main phases and deadlines for each of these phases.

Phase 2

The migration begins with the configuration of the testing environment, which is moving Magento 2 onto a new server. In this phase we deal with the graphic themes, enhancements, plug-ins, data and content, which will be transferred from Magento 1 to Magento 2.

Phase 3

We carry out purchase history and customer data synchronization in order to increase swift change from Magento 1 to Magento 2.

Our knowledge

Your benefits

Certified Magento developers

In our team, we have certified developers that are experts in their field. Our specialty are comprehensive implementations of e-Commerce platforms with Magento software.

Certified Magento developers
Certified Magento developers
Certified Magento developers
Certified Magento developers

Our metodology

THE AIM OF THE PROCESS IS TO GATHER INFORMATION ABOUT THE PROJECT:

  • Customer market.
  • The most important project requirements.
  • Project objectives.
  • Main assumptions and project constraints.

THE AIM OF THE WORKSHOP IS TO GATHER INFORMATION ABOUT:

  • Business requirements.
  • Processes.
  • Business rules.
  • Usually the workshop takes 1-2 days, it can also be divided into smaller batches in case of necessity of involvement of many project stakeholders responsible for particular fields of project activity and is concluded with preparation of a preliminary estimate.

THE AIM OF THE WORKSHOPS IS:

  • Identifying the main stakeholders of the project.
  • Creating the so-called person – the profile on an ideal recipient.
  • Preparing functional mock-ups.
  • The process of preparing the wireframes takes from 2 to 3 months.

DETERMINATION OF TECHNICAL ASPECTS OF IMPLEMENTATION SUCH AS:

  • Discussing the business model.
  • Systematising the functional backlog.
  • Defining implementation elements, developing user stories and acceptance criteria for tasks
  • Using the MoSCoW (Must, Should, Could, Won’t) analysis, define the tasks necessary to implement the MVP version.

DETERMINATION OF TECHNICAL ASPECTS OF IMPLEMENTATION SUCH AS:

  • Integration methods.
  • Variables used when querying specific methods.
  • Prioritization of querying methods and communication directions.
  • Preparation of technical documentation usually takes 2 to 4 weeks.

Approval of the specifications

Confirmation of the documentation findings and prioritization, if not prioritized in earlier stages.

Proper project valuation

Based on the collected information, mock-ups, functional and technical documentation, the tasks are re-estimated and the quote is confirmed.

DESIGN OF PROPOSALS TO BE PRESENTED TO THE CLIENT:

  • Preparation of initial graphic proposals based on the requirements from mock-ups developed during the analysis.
  • Acceptance of the finished designs by the client.
  • Iterative creation and approval of graphics for subsequent pages.

PREPARING THE DEVELOPMENT ENVIRONMENT AND PLANNING SPRINTS:

  • Sprint start – Planning the team’s work with the product owner.
  • Analysis – Detailed technical discussion of tasks.
  • Daily – Daily meetings to summarise progress.
  • Refinement – Dedicated meetings with the architect/team leader to increase the team’s understanding of tasks.
  • Sprint summary – A summary of the team’s work and presentation of progress in practice.

DURING TESTING WE FOCUS ON:

  • Preparation of the pre-production UAT version and final confirmation of the implemented functionalities.
  • Performance tests of the finished product, eliminating any errors before the implementation of the production version.
  • First production migration and data integrity verification.

Deployment

Implementation of the project in the production environment, during which the missing data are migrated and launch of the product.

OPTIMISATION

  • Deployment of the system based on the backlog of works.
  • SEO optimisation.
  • Automation.
  • Integration of sales tools.

How we can help you

Contact us

Estimate your project

Write to us

Pole jest błędnie wypełnione. Sprawdź wpisaną treść i spróbuj ponownie.
Pole jest błędnie wypełnione. Sprawdź wpisaną treść i spróbuj ponownie.
Pole jest błędnie wypełnione. Sprawdź wpisaną treść i spróbuj ponownie.
Pole jest błędnie wypełnione. Sprawdź wpisaną treść i spróbuj ponownie.
Wyrażenie zgody jest niezbędne.

PDF, DOC, DOCX, JPG or PNG (max 5MB)

Failed to send your message. Please try later or contact administrator by other way.
Andrzej Szylar

Andrzej Szylar

Chief Executive Officer

Dariusz Kobza

Dariusz Kobza

PR & Marketing Manager

Magdalena Paczynska

Magdalena Paczyńska

HR Business Partner