Plan an agency CRM migration around the records and active work the team needs to continue. Inventory the data, decide what moves, map fields and relationships, and test a small sample with appropriate permissions. Agree on the transition and acceptance checks before making the new system the place where staff begin work.
A CRM migration can look like a file transfer while actually changing the way an agency finds and manages client work. Contact names are only one part of that work. The team may also depend on engagement history, open opportunities and information that lives in another tool.
This checklist helps define the scope. It does not promise a migration outcome, timeline or capability for a particular product.
- Map the recordsDefine fields, relationships and the authoritative source.
- Test a sampleInclude returning clients, multiple contacts and active work.
- Reconcile the resultCheck values, permissions and the tasks staff need to perform.
- Accept the moveAgree on the cutover, issue owners and recovery procedure.
An imported row count is one check. Acceptance also requires the team to find and use the right information.
What must survive the move?
Ask sales and delivery to identify the information they need for current tasks. Follow an active engagement to see which records, attachments and conversations staff actually use.
Include relationships between records. A company with several contacts, a returning client with another engagement, or an opportunity linked to an approved proposal can become difficult to understand if the relationships are lost.
Keep an inventory that distinguishes active work from historical information. Decide what must be imported, what can remain accessible elsewhere and what belongs in an approved archive.
What can the source and destination actually handle?
Confirm export options in the current source system and import options in the proposed destination. A contact export may not include every associated activity, file or relationship.
Request a field-level description of the supported transfer. Check formats, required values and limits. If some information cannot move automatically, describe the manual work or archive arrangement needed.
Do not treat a general “migration support” statement as a complete scope. The agency needs to know which parts of its own workflow and data are included.
How should fields and relationships be mapped?
Create a mapping sheet before the full import. Record the source field, destination field and any transformation or review required.
- Client identityDefine company and contact matching.
- Opportunity stageTranslate source meaning to destination process.
- Record ownerTransfer responsibility to authorized staff.
- Unsupported dataAssign exception owner and archive decision.
Send uncertain duplicate matches for review instead of silently merging them.
| Mapping item | Decision to record |
|---|---|
| Client identity | How the destination identifies the right company and contacts |
| Opportunity stage | What each source stage means in the destination process |
| Record owner | How responsibility transfers to an authorized staff member |
| Engagement reference | How the client remains connected to the work being delivered |
| Notes and activity | Which information imports, stays in an archive or needs review |
| Exceptions | Who handles missing values, conflicting matches and unsupported data |
Define duplicates deliberately. Two records with a similar name may be different companies, while one client may appear under several spellings. Send uncertain matches for review rather than silently merging them.
Which permissions need to be preserved?
Describe the people who need access and the work they should be able to do. Check the destination with appropriate test accounts before exposing imported information broadly.
- Destination staffDefine work each person needs.
- Test accountCheck destination access before broad exposure.
- Historical rulesDo not assume old permissions transfer.
- Client viewReview separately from internal workspace.
Confirm ownership and permissions in the destination's actual model.
Historical access rules do not necessarily transfer with the records. Confirm ownership and permissions for the destination's actual model. Review what clients can see separately from the agency's internal workspace.
The client-data security guide provides questions about access, offboarding, exports and vendor responsibilities.
How do we test a representative sample?
Choose sample records that exercise the important relationships. Include an active client, a returning client, a company with several contacts and an opportunity that needs the delivery team to find the approved scope.
Where possible, use sanitized data to test the mapping before handling live client information. Ask the staff who will use the destination to complete their normal tasks with the sample.
Check both the imported values and the business meaning. A stage name can import successfully while putting the engagement in the wrong part of the process.
What happens to work in progress?
Agree on the point when new records begin in the destination. Describe how changes in the source will be handled during the transition and who resolves discrepancies.
- Cutover pointDecide when new records enter destination.
- Source changesDefine handling during transition.
- Discrepancy ownerResolve conflicting current values.
- Recovery procedureKeep original information accessible.
Parallel access needs a stated purpose and a responsible coordinator.
Avoid leaving the team to guess which system contains the current value. If parallel access is needed, define its purpose and the person responsible for coordinating it.
Keep the original information accessible according to the agency's approved retention and security practices. Document the recovery procedure if the move does not meet the acceptance checks.
What counts as an accepted migration?
Agree on the checks before the full move. These should cover records and the staff's ability to continue work, rather than only the number of rows imported.
Illustrative acceptance checks: the delivery owner can find an active client's approved scope; the opportunity has the appropriate sales owner; a returning client is not duplicated incorrectly; the required test roles have appropriate access; and unsupported information has an agreed home.
Identify the person who accepts each part. Keep unresolved issues visible, including those that need a process decision rather than another technical import.
How should we scope help from a provider?
Separate data transfer from workflow configuration, integrations, training and support. Ask what the agency must prepare and which assumptions could change the proposed scope.
If you are considering ScaleAxis OS, review its beta terms and contact ScaleAxis before migrating. The GoHighLevel comparison states that ScaleAxis import formats are not yet published. The other current comparison pages carry the same limitation.
An operations audit can be a starting point for discussing the current workflow. It should not be treated as a confirmed migration commitment. Agree on supported systems, scope and recovery arrangements before the agency commits to a move.
Questions and answers
What should be included in an agency CRM migration?
The scope may include contacts, companies, opportunities, engagement details and associated activity. Decide which records need to move and which should remain in an approved archive. Confirm the source exports and destination imports before promising that all information can transfer.
How long should the migration take?
The timeline depends on data quality, supported formats, relationships, active work, integrations and review. Request a scoped plan with assumptions and acceptance checks. Test a sample before accepting a timeline for the whole move.
Should we move every old record?
Not automatically. Establish what the team needs, what must be retained under the agency's policies, and where it belongs. An archive can be appropriate for some historical information, while active client work needs deliberate continuity.
Can we migrate straight into ScaleAxis OS?
Contact ScaleAxis before planning that move. Its current comparison pages say import formats are not yet published, and the platform is in beta. Confirm the actual supported source, fields, limitations and recovery arrangements for your use case.